agogosml should use a single container per model

[DanMass]

The three containers add to overall runtime complexity and increase build times while making it harder to maintain the semantics of the queue/stream to which the containers are connected. Much can go wrong in the two extra http hops. Given how we create agogosml apps/containers from templates, we could easily create a single-container template.

agogosml is currently a more brittle (at runtime), less capable model hosting environment than Kafka Streams ( https://kafka.apache.org/21/documentation/streams/core-concepts ). We should simplify agogosml with the idea of moving over to Kafka Streams when the Kafka head for Azure Event Hub supports it.

[sayar]

I added a user story in the backlog to create a single container template. There is some minor work for the CLI but should be possible in this or the next sprint.

[DanMass]

I'll try to help, especially if it's next sprint.