#Application Architecture Question

10 messages · Page 1 of 1 (latest)

dusty lake
#

(Pardon my shitty drawing)

Essentially App 1 (you can think of it as a spring-boot or other full stack 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?

image.png
stable oreBOT
#

⌛ This post has been reserved for your question.

Hey @dusty lake! Please use /close or the Close Post button above when your problem is solved. Please remember to follow the help guidelines. This post will be automatically closed after 300 minutes of inactivity.

TIP: Narrow down your issue to simple and precise questions to maximize the chance that others will reply in here.

green nova
#

i don't know what broker you are/want to use but you can generally clear a queue by consuming from it (e.g. from the app) if you don't want the renderer to access now out-of-date messages

signal mantle
#

Why would you want to render (and what kind?) something so deep in the stack?

stable oreBOT
#

💤 Post marked as dormant

This post has been inactive for over 300 minutes, thus, it has been archived.
If your question was not answered yet, feel free to re-open this post or create a new one.
In case your post is not getting any attention, you can try to use /help ping.
Warning: abusing this will result in moderative actions taken against you.

dusty lake
dusty lake
dusty lake