Anders Sveen

Firebase is a lot of different things. :) I have good experience with the authentication part, but you need somewhere to store the information about your users. It only handles the actual authentication part. You can of course use Firebase DB, or just Postgres (somewhere else) to store that.

You should really consider whether the type of technology suits your application. Firebase is a pretty good alternative if you want to use cloud functions, document database etc. But AWS and Azure also offer good alternatives. If you'd like a relational DB Firebase is less of an option.

I would say that getting everything tied together without a deeper knowledge is probably easier in Firebase than Azure though. :)

We use Heroku because it's easy and fast. We spend 0 time on DevOps stuff (and I've spent a lot of time on that before), and it just keeps running. One click install of add-ons, and consolidated sign on with billing is awesome.

If you're going to use a lot of memory or run many processes it gets expensive fast. But you probably shouldn't use that much memory and you rarely need to run many processes. Heroku will start a new process if one dies (rare), so if you need extreme up time you can pay for running multiples. :)

Their support is stellar even though we don't pay for top tier support. Since we're off timezone wise it might take some time to get responses. But they always connect me to someone with deep technical insights that give concrete feedback and helpful information even when my problems are of the less common ones.

I use Coralogix because it integrates seamlessly with Heroku and has great defaults for most things. While other solutions have more features, they usually require some setup before proving useful. Coralogix just works out of the box.

Oh, and their support is super responsive and nice. :)