Skip to main content

My experience with firebase

I started using firebase for one my project for the past couple of weeks now, and it has its ups and downs to say.


Initially, I had a very warm relationship with firestore and authentication when I used the later for one of my world cup prediction app. Which after a little bit of struggle I managed to make it work.


I thought this is cool. I should use it more often.


Then I created a blood donation app using firebase this time, using its authentication and as well as a firestore feature to store the info relating to the blood groups of persons who are registering to the app.


But then I see problems.


I see that its not easy to take the counts of people who have O +ve blood, you just need to keep that glued in somehow (I used a counter variable if you ask me!), and then needs to update two or three places in order to run the app smoothly(hey, its NoSQL what do you expect!).


I was running the code here and there updating the firestore DB multiple times increasing my read and write a little bit up I say.


But then my company told me to do an enterprise solution app on firebase.


That's when it hit me, hit me hard in reality.


I wasn't aware of the full capability of this wonderful tool. Then suddenly I am designing a database for firebase. Unlike SQL database structure were I take great care not to repeat fields over and over again, I am designing an app that is full of chaos but the only thing I need to consider here is the cost of my client, how well am i going to design this DB so that my client only needs to pay for what he sees on the dashboard.


I am still in the process of finishing phase 1 of my app (at least while I am writing this post).


I think firebase is going to be one of my best friend in the upcoming weeks.


I will keep you updated on my story.


At the end in every relationship, you will have ups and downs.

Labels:

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

A smoooooth operation....

 Backward compatibility...   A word that I used to hear when I started my career. You design your APIs with backward compatibility in mind, don't break anything when you are upgrading, think about this, think about that etc. Well, those teachings from my previous mentors didn't go in vain, as I made a fundamental change in how we report problems @  Gelato .    You see recently @  Gelato , the CS (Customer Support) team moved from A ticketing management system to B ticketing management system, which is a monumental task for all the people involved in the CS team. Even though the fundamental concept remains the same the places, the attributes the concepts, and the naming of different attributes all change if you have this transition. And thus it was a big change for the whole company.    After the decision was taken, the first step was to create a well-written transition document, which the good folks at the CS team tackled. Special thanks to  Bartosz ,  Kyle  and  Anastasiia  fo
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