Databases
StackOverflow2013
Postsdbo
POSystem architecture for location-based message system using message queues
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSystem architecture for location-based message system using message queues
    text
    copied!<p>I'm currently designing a mobile application that can send and read messages to a timeline based on users location. Actual development version is using <strong>ActiveMQ</strong> to send and consume messages, but it's still not finished so I prefer to define how the architecture should be to avoid future problems before continuing the development. I'm not sure that this is the correct approach, but here's what I thought:</p> <ul> <li>Every user is a producer that sends message to its queue. Queue name could be user's unique ID.</li> <li>Users can subscribe to others users queue, if they're close enough. This involves something like <em>Topics</em> to a group of users queues. This queue should be dynamic, generated by retrieving the users that are inside a fixed radius, being the center of the circle the position of the consumer. Each user would have it's own <em>Topic</em> or <em>queue</em> like this one (very similar concept to Twitter's timeline). This means that each user queue will have more than one consumer.</li> </ul> <p>From the client side, I've been using an Objective-C stomp client as the connectivity protocol with the queues.</p> <p>My question is, is this a good approach to the problem? I'm not sure that the user subscription to near users is a feasible architecture with ActiveMQ and <em>Topics</em>. Do you have any suggestions to this timeline-subscription problem? On the other side, it's clear to me that every user needs to be the producer for its own queue, but maybe I'm wrong too.</p> <p><strong>EDIT</strong></p> <p>Any reference, link, book, etc. with more info about the subject will be highly appreciated.</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload