Home/ Questions/Q 6350197
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-24T21:45:57+00:00

I am designing an application and I have two ideas in mind (below). I

  • 0

I am designing an application and I have two ideas in mind (below). I have a process that collects data appx. 30 KB and this data will be collected every 5 minutes and needs to be updated on client (web side– 100 users at any given time). Information collected does not need to be stored for future usage.

Options:

  1. I can get data and insert into database every 5 minutes. And then client call will be made to DB and retrieve data and update UI.

  2. Collect data and put it into Topic or Queue. Now multiple clients (consumers) can go to Queue and obtain data.

I am looking for option 2 as better solution because it is faster (no DB calls) and no redundancy of storage.

Can anyone suggest which would be ideal solution and why ?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I don’t really understand the difference. The data has to be temporarily stored somewhere until the next update, right.

    But all users can see it, not just the first person to get there, right? So a queue is not really an appropriate data structure from my interpretation of your system.

    Whether the data is written to something persistent like a database or something less persistent like part of the web server or application server may be relevant here.

    Also, you have tagged this as real-time, but I don’t see how the web-clients are getting updates real-time without some kind of push/long-pull or whatever.

    • 0