Parse gives you another way to ignore the server
Posted by Dion Almaer 11 months ago on db noserver parse
Parse is an interesting YC company that created a datastore++ in the cloud originally focused on mobile clients (iOS and Android).
While there are plenty of folk who were willing to bet only on one or both of those platforms, there are a huge number of companies that want (or need) a Web experience of some kind, and although going directly to the REST API is an option, it wasn’t ideal.
If you are the type of developer working on the type of problem where you are happy to be server agnostic and just focus on the client, and you can life within those constraints, then this could be a great solution for you.
The JS SDK has been built on top of Backbone, which is a very natural fit as you can see by checkout out a port from Backbone models and Parse-backed models.
Meteor shot onto the scene. It also allows you to ignore your backend, but focuses on Web apps and is great for real-time event based communication. Parse doesn’t seem to offer native Web Socket / Socket.IO support, but it does have access controls baked in. This was something that folks called for in Meteor…. the idea of being able to db.remove({}) via the console is one you obviously need to guard against. Don’t trust defaults!
In the same area we also have Firebase, which was recently funded.