alanlbird

I'm a bit surprised at the negativity here. I have used Firebase for 11 projects and have had no issues at all. I love that I can quickly and easily set up services that work well together.

For most projects I use the realtime database and authentication. The database is very fast and the realtime feature is essential for some of my projects. Authentication is free no matter how many monthly users I have.

I also use storage and hosting, where I get excellent performance.

All but one of my projects work within the free tier. The one project that sometimes exceeds the free tier is generally less than $1 per month. My projects are fairly small, but I know that for large projects, there might be more economical solutions somewhere else.

For me, I would highly recommend Firebase to other developers.

I recently did a pricing comparison of cloud object storage services for my article "How to Create a Very Inexpensive Serverless Database" (https://aws.plainenglish.io/very-inexpensive-serverless-data...). It describes using object storage as an inexpensive serverless key-value database.

Although egress (outbound network) can be a significant part of object storage expenses, if you are reading and writing small objects, per-request expenses can be much bigger. Cloudflare indicates that for low request rates there won't be any request fees, but doesn't state what they will charge for high request rates.

My article points out that the best deal when working with high request rates is to use services that don't charge per request such as DigitalOcean, Linode, and Vultr. If it's S3 that you want, even Amazon has recently joined the budget club with Lightsail Object Storage which has monthly plans of $1, $3, and $5 (250 GB storage and 500 GB egress) with no per-request fees.