Firebase wants to take the headache out of building full-stack JavaScript apps (and mobile) by taking care of your back-end and authentication for you.

But first a little background…

When I first got into the idea of full-stack Javascript about 6 months ago, my first step was to start playing around with Node.js and then Angular trying to connect the two but I quickly became frustrated with every step requiring me to learn some new component that would make my life easier (Bower, Gulp, Grunt, Sass, etc) but only after I’d got up the learning curve. Each time becoming another step removed from just writing some code of my own.

In the end I put it all to one side and just focussed on building an entirely front-end single page app (SPA) in pure Angular so that I could learn some of the principles without the clutter and confusion of working out what was doing what. Fortunately I’d chosen a little toy project that didn’t require me to build a back-end as I was building on top of Spotify’s API – mixtaper.net.

Anyway, at that time I did look into a couple of Backend-as-a-Service (BaaS) providers, including Parse, whom I see today are shutting down their service and releasing some of their code into the wild for people to use on their own servers. A shame for them – the absence of reasons in their statement I suspect means it’s down to not being able to sufficiently monetise their product. I guess the BaaS area will become commoditised pretty soon with Google, Amazon and others fighting to be the Supreme Cloud.

One thing that might help Google with that is their acquisition in 2014 of Firebase which is really what I’d planned to write about but maybe I’ll just leave this post here as a thought on getting started in full-stack JavaScript (too many things you might or might not have to learn) and on the future on BaaS (probably a race to the bottom on pricing which will be won by the players that can afford to make a loss until hardware costs catch up with their low prices and until after the competition are gone).

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>