3 ms·
Thank you for sharing. I was actually thinking of using fire base for my project. They make us so easy to sign up for free tier. Awaiting to see what happens
by pettycashstash2 6y ago
Thank you for sharing. I was actually thinking of using fire base for my project. They make us so easy to sign up for free tier. Awaiting to see what happens in part 2
- bharatsb 6y agoPart 2: https://blog.tomilkieway.com/72k-2/ https://blog.tomilkieway.com/72k-2/
- spacemanmatt 6y agoI recently put the (soft) kibosh on a project in my stable trying to switch to FireBase at the last minute. It looks attractive but the business aspects are frankly frightening, and I'm not even talking about the risk of a large bill. Getting your metrics 24h late sounds like a deal killer for me. So much for observability!
- asciimike 6y agoMinor nit: many non-billing metrics are near-real time, e.g. DB concurrents, cloud functions CPU/RAM usage; any metrics that require aggregation (storage, billing) are going to be batched less frequently. This is going to be true across all platforms of non-trivial scale (eventual consistency + batch jobs). Second note: the number of people who actually do this is very low (a few a year, of hundreds of thousands of developers). The blog posts are scary, but in my ~five years at Firebase, I'm pretty sure we refunded every one. As my boss (James Tamplin, CEO of Firebase) used to say, "There are lots of bad systems, but rarely are there bad people."
- spacemanmatt 6y ago> I'm pretty sure we refunded every one. That's good to know. It seems like a particularly visible part of the cloud credibility puzzle to be able to monitor/limit dynamic resource costs.