Google's Firebase — back-end-as-a-service

Firebase is a mobile platform that makes it easy to write for mobile, deploy those apps, and to earn money doing so, providing an end-to-end solution.

I wonder why another category of "back-end-as-a-service" is necessary. We already have infrastructure, platform and software-as-a-service. Why we can’t just use one of those systems and integrate it with your front-end?

Is this just a naming issue, or is there something fundamentally important about having a BEaaS provided to developers?

back-end-as-a-serviceAs with most developer-oriented tools, it’s a matter of convenience. Craig Wright, a friend of mine has written a Game of Thrones "death pool" app. (If you want to try it, it’s at  You play by betting play-money on who will die in the next episode of Game of Thrones. Craig was able to do it in a short amount of time, and has used Facebook’s React JavaScript library as the front-end.

So it's beginning to make sense to me. Even for an experienced programmer like Craig, saving time is always a benefit.  Anything to get rid of the back-end drudgery to focus on what really matters to the developers — improving the front-end end-user experience — makes sense.

Since Firebase is packaged as a single SDK, you don’t waste time gathering different back-ends and suffering through incompatibility and version issues. Finally, adding analytics, driving traffic and ad display is built-in to the system.

If you insist on using different components, you can always do that. But if you want an app to be up and running quickly, leveraging a BEaaS saves time.

So in the same way as PaaS (such as Cloud Foundry) that automates application lifecycle, it is also useful to simple the whole application back-end.

campus network 

Topics: Networking Cloud Services & Orchestration