Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

11
  • 1
    This assumes a single process reading from the queue at a time. There are lots of reasons that can be problematic. Commented Jul 31, 2024 at 18:13
  • Given the clarification, this is a good solution. Consider using a queue per client or something like message attributes to allow for concurrent processing of multiple client requests. Commented Jul 31, 2024 at 18:29
  • it's not so much assuming as specifying. If you split the application up you can control where you need to be synchronous and asynchronous Commented Jul 31, 2024 at 18:56
  • If you have multiple processors on a queue, FIFO isn't guaranteed (or even expected), at least with the various messaging platforms I've worked with. That requires some sort of distributed semaphore or other enforcement of order. Generally, not worth the problems that come with that, in my experience. Easier to deal with at the DB. Commented Jul 31, 2024 at 19:11
  • sure theres no free lunch, ive updated my answer to go into it a bit Commented Jul 31, 2024 at 19:15