Skip to main content

My story of infinite loop on firebase...

 

 So recently I heard the news of a startup "Announce" getting a bill of $72k and almost bankrupting them in the process.


Story can be found here.

When I heard the news I was thinking about the same mistake that was made by me.


if you are a programmer, chances are that you heard about good old recursion. Recursion is a powerful strategy for solving problems, but with great power comes of course great responsibilities. Missing an edge case in a recursion can cause a huge conundrum and your resources getting exploited pretty quickly, all thanks to the infinite recursion that's been happening on the background.

Now in the cloud, recursion is little bit of the same line but brings forth another set of problems as well.
In my case, I wrote a cloud function in firebase, that will update the date of a set of documents inside a particular collection when data is being **modified** in the same collection. Yes I know, dumb! I thought of making the cloud function such that when new data is being **added**, please update the date. But lucky me, instead of **adding**, I put **update**.

And that cause recursion of it's own.
But I was lucky enough, such that at the time of programming, in order to use a cloud function I didn't needed a credit card (which is not the case as of now!).

But this is just an absolute dump move, from a newbie in cloud computing. Which indicates that even a newbie should be pretty careful to use the cloud features with its upmost care.

Even experienced devs, accidentally introduced cloud recursion that gave them huge amount of bills.

So next time you use a cloud service, make sure that you enable the option to trigger an action while your bill reaches a certain amount. Most popular cloud services like AWS, and GCP provides this feature.

Comments

Post a Comment

Popular posts from this blog

AI. Will it replace us or...?

AI!! The buzzword is too hot in the market nowadays. Do you have a technical product or an idea? If it doesn't have AI in it, then chances are it's not going to be sold like hot cakes. That is how things have changed lately. It is no wonder why me and my colleagues at Gelato want to see what AI can do in a niche department like customer support and service. And that is exactly what we did. For a company like Gelato, which is in the market for production-on-demand, there are a lot of customer questions you need to answer. It can be related to products, queries about shipping and pricing, and so on and so forth. Thus, our customer support team is always happy to help with these recurring questions. Let's take one example. A customer asked us, "Do you ship to Norway?" Now that is an easy question to answer if you have the knowledge written somewhere where you could refer to it and say, "Yes! As a matter of fact, we do." Following the same thread, the next q...
Post a Comment
Read more

Replication and transactional guarantee in MongoDB

One of the projects I am working on is using MongoDB as the database solution. And the project makes use of the nifty ORM mongoose to do the heavy lifting of data orchestration. It was high time I implemented transactions to the equation but because of a time crunch I was not able to start with one and the situation merely demands it at times. But come with an architectural change and the way the project was heading it was high time I implemented transactions by using MongoDB. According to MongoDB documentation, transactions are used when the situation requires, “atomicity of reads and writes to multiple documents (in single or multiple collections)”. MongoDB supports multi-document transactions. With distributed transactions, transactions can be used across multiple operations, collections, databases, documents, and shards. Now the piece of code to implement the same was pretty straightforward. // For a replica set, include the replica set name and a seedlist of the members in the URI...
Post a Comment
Read more

My experience with the Golden signals

In June 2022, I embarked on a quest for a new job opportunity. Fortunately, this endeavor began just before the global job market experienced a significant downturn. I must admit, I faced my fair share of rejections during this period, but I also had an epiphany. It became evident that there was so much more to learn and understand in the world of technology. Coming from a small service-based company, I had encountered limitations in terms of how much I could learn on the job. However, during interviews and conversations with senior developers, I gained valuable insights into the architectural and technical decisions made by teams in various companies. One such company that left a lasting impression on me was Delivery Hero. Their technical blog posts provided a wealth of information, especially for someone like me, transitioning from a smaller company where projects had minimal daily active users compared to the scale of Delivery Hero. One particular blog post that caught my attention ...
Post a Comment
Read more