This concept covers object-oriented library design, specifically how a well-designed API expresses common abstractions (such as a language model, prompt template, or output parser) through a shared interface with multiple interchangeable or specialized implementations. It draws on classic object-oriented design patterns — strategy (swapping interchangeable algorithm implementations behind a common interface), bridge (decoupling two independent implementation hierarchies so each can vary without affecting the other), and template method (defining a fixed sequence of operations that delegates specific steps to pluggable objects) — as illustrative structures rather than rules to be followed literally. The domain is software engineering / object-oriented design principles, situated within the broader discipline of software architecture, where the underlying design principles (coupling, cohesion, separation of resource-creation from resource-use, simplicity) are treated as more fundamental than any single named pattern.
This concept covers object-oriented library design, specifically how a well-designed API expresses common abstractions (such as a language model, prompt template, or output parser) through a shared i…