0

we would like to develop a real time event driven chat app for mobile. Our system will have peak user connections in the some parts of the day. We want to handle all of those connections without hassle. To do this, we are thinking to develop or use a third party API(like in Firebase).

We, however as an inexperienced startup developers - we developed only 1 project as a team before in ASP.NET, - could not decide which to choose. Which would be better, if we set up everything ourselves and use Node.js, Socket.io, MongoDB and our servers, or we thought to using Parse, or Firebase - they also both have positive sides and drawbacks.- We also open to another suggestions.

We want rock-solid entrance to the market so and we also have low budget initally. But it is possible we may go invitation-only app, then later we grow our userbase. Thanks in advance.

msharpp
  • 379
  • 1
  • 6
  • 20
  • Checkout Realtime Framework (http://framework.realtime.co) to handle your event emitting/subscribing between devices at scale. Currently over 500 million MAUs. – João Parreira Jun 10 '15 at 13:55
  • 1
    From my point of view, Parse and 'Real Time' can't stay in the same sentence XD. Parse does not provide a socket support, and the only way to make something almost realtime, is relying on the push notification ( supposing users will allow it on their device ). Better to use a NodeJS service instead – Luca Iaco Jun 10 '15 at 14:41

0 Answers0