How should I abstract the LLM provider (Ollama → Bedrock/OpenAI)?
Build one narrow complete(prompt, opts) interface with three implementations picked by config, and treat context window, latency and cost as config.
Tag
Design choices that set system boundaries, dependencies and the decisions you cannot undo. (Page 2/2)
13 answered questions carry this tag.
Build one narrow complete(prompt, opts) interface with three implementations picked by config, and treat context window, latency and cost as config.
Don't make EFS the interim step; switch to a Flysystem s3 disk, route reads and writes via Storage::disk(), and migrate with dual-read for zero downtime.
For heavy Laravel-Go traffic pick Protobuf plus a schema registry, keep JSON Schema for light traffic, and deserialize into a typed DTO at the boundary.