Skip to main content

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*

5
  • Hi, Thank you very much for your detailed response, but I didn't understand which DB you would really suggest using, I am sorry but I don't have enough experience in this field. I will definitely check the event driven architecture using a 3rd party solution for my purpose. I assume that you refer to queues for the side that sends notifications to devices? I know that for Android you must use some Google service which is also based on queues I think, but there are several other services built on top that provide easier APIs - Am I right? Again I am really a beginner... Commented Nov 12, 2014 at 8:53
  • There are dozens of different ways to accomplish what you need. I'll edit the answer and lay out 3 concrete ones and try to answer your question about DB. Commented Nov 12, 2014 at 14:11
  • Hi, Thank you very much for the detailed answer. I think I will stick with the third option "Java Netty + RabbitMQ + MongoDB" as I have experience with JEE (specially server side). I understand that mainly I will have to learn Netty as I am not familiar with that. As regards to MongoDB - there are no problem with the amounts of reads & writes? Commented Nov 12, 2014 at 18:18
  • Mongo should be able to handle all of your read/write needs. You can scale it up quite easily if your applications grows beyond just one server. Good luck! Commented Nov 12, 2014 at 18:46
  • Also look at XMPP while developing instant messaging. Its a complete different protocol/architecture. Commented Sep 25, 2015 at 6:07