A model type categorizes models by their input/output format and data-processing logic. Different types usually require distinct interfaces, preprocessing, postprocessing, and caching behavior. section 6.3.2
Design implications include:
- Run separate prediction services when model types have substantially different interfaces or processing logic. section 6.3.2
- Give each service its own model cache and model-swapping behavior. section 6.3.2
- Reconsider this architecture when supporting many model types because service deployment, monitoring, and maintenance costs accumulate. section 6.3.2
Image and intent classification
An image classification service and an intent classification service can remain separate because their input/output formats and processing logic differ. section 6.3.2
Use the prediction-service architecture to inspect how model caching supports multitenant requests. section 6.3.2
