An inference graph coordinates multiple models and services during inference instead of packaging them as one opaque service. This matters when a workflow combines an encoder, language model, classifier, and API, or when components need independent scaling and updates. section 6.2.4
Separating components creates practical deployment benefits. An encoder can be reused for preprocessing and VectorDB population, while the API can change without redeploying the language model. Independent model APIs also allow different component counts, such as one encoder for every two or three language-model instances. section 6.2.4
Seldon deployment
A Seldon Deployment extends Kubernetes with an orchestrator that runs graph components in order. A representative configuration connects an encoder, combiner, language model, and classifier through REST model endpoints.
