As an ML engineer,
I would like to merge the transformer and predictor steps that make up the outlink articletopic model, so that I can:
- better manage resources as I will be creating 1 pod instead of 2 for each replica
- make code abstractions and communication to Cassandra easier in T401778: Evaluate adding caching mechanism for article topic model to make data available at scale
In T287056: Deploy Outlinks topic model to production we deployed the articletopic outlink topic using the transformer-predictor paradigm from kserve. This paradigm is a great one if we want to generalize and re-use the same transformers in multiple services/models.
However, since there is no pattern of reusability here we would like to merge this in one step. This would result in a single-file declaration of the kserve model in the same way that we do in the other services that we run.