Many times my mobile apps need a remote or a shared database, but often they need nothing more than only that: the mobile client and the remote database. I could write a new RESTful server for each of those apps but when the app needs only standard CRUD operations, writing a new REST server each time feels like overkill. (And connecting directly to a remote database over the Internet is a horrible evil idea!)
This is where Parse.com shines: it provides REST services, authentication, user management, security, and data storage, letting me focus on writing just the client code and the database design. It lets me deliver an N-tier app but build it as if it were just a simple 2-tier app, leveraging a NoSQL database that “feels” like it is connected directly to my mobile app. (Parse uses MongoDB and Node.js behind the scenes.) Parse also provides very nice SDKs, providing full support for features like async processing in C#/Xamarin (my mobile platform of choice!), JavaScript, and Objective-C among others. Parse also provides much more: the ability to run arbitrary JavaScript code, easy support for push notifications, hosting of static HTML pages, and more – but for simple apps, the basic data storage and REST services are all I need.
Moreover, Parse provides a very generous free tier so I can get started on an app or prototype an app for a client for no cost, then scale it up into the paid tiers when the app grows or traffic spikes.
I highly recommend it!
(Apparently I’m coming fairly late to the “Parse” party – it seems like many others already knew about this gem. Now that I’ve finally tried it, however, I’m kicking myself for not using it earlier so I’m doing my part to get the word out. And no, I have no connection whatsoever with Parse.com other than being a fan.)