Application Architecture Question
(Pardon my shitty drawing)
Essentially App 1 (you can think of it as a .NET or other application) passes Json messages via a MQ to a rendering app. I'm using a MQ because I want the messages to be received in order.
We want to build up the rendered environment in the renderer progressively using json generated by user input from App 1.
My question is, is this architecture 'correct' or does it make sense for this use case?
Is there a better way to do this?
What kind of timeout makes sense to wipe the queue so that the renderer (subscriber) doesn't accidentally access messages from a previous run/activity?
Essentially App 1 (you can think of it as a .NET or other application) passes Json messages via a MQ to a rendering app. I'm using a MQ because I want the messages to be received in order.
We want to build up the rendered environment in the renderer progressively using json generated by user input from App 1.
My question is, is this architecture 'correct' or does it make sense for this use case?
Is there a better way to do this?
What kind of timeout makes sense to wipe the queue so that the renderer (subscriber) doesn't accidentally access messages from a previous run/activity?
