How Hasura is fundamentally different from a Firebase or Parse
(This post was originally published on Jan 28, 2016)
Today, Parse announced that they are winding down the Parse service. It’ll be completely retired in an year. What Parse started was amazing: making it super fast to set up applications on the web and mobile. But with it shutting down, the developers who built apps on Parse are now faced with two difficult choices:
- Migrate to another BaaS (and risk this whole episode again).
- Run their own backend (comes with its downsides).
Developers will now be skeptical about using any BaaS. It can be acquired and shut down. They have every reason to be.
Hasura is a platform for building scalable backends. It is however built around this core philosophy:
Developers should have complete control over their backend.
With Hasura, every app can get its own backend and run on its own dedicated server (or a cluster) unlike a monolithic service that serves every app (like Parse, Firebase, etc). This gives you as a developer, a unique ability to completely customise your backend, but only if you need to.
In short, we are as dev friendly as Parse or Firebase and as customisable as GCE, AWS or Azure. So, there will never be a question of moving away from Hasura; you are not locked in to begin with.
Update 1: This is what Charity Majors, former infrastructure tech lead at Parse, had to say about Hasura.