Vishal Agarwal

People start off on Monday eating salads and finish off the week eating pizzas on Fridays and Saturdays. And guess what is the most ordered delivery item? It's pizza, right? This was not built for scalability. I told you we were super happy when we started hitting 10,000, 50,000 orders a month.

People start off on Monday eating salads and finish off the week eating pizzas on Fridays and Saturdays. And guess what is the most ordered delivery item? It's pizza, right? This was not built for scalability. I told you we were super happy when we started hitting 10,000, 50,000 orders a month.

People start off on Monday eating salads and finish off the week eating pizzas on Fridays and Saturdays. And guess what is the most ordered delivery item? It's pizza, right? This was not built for scalability. I told you we were super happy when we started hitting 10,000, 50,000 orders a month.

And as we grew, we realized the systems that we had to build, the queuing servers, the scaling mechanisms changed. We were on Heroku and about two years ago, we migrated everything to AWS, which gave us a lot more control, a lot more flexibility and the ability to scale, right?

And as we grew, we realized the systems that we had to build, the queuing servers, the scaling mechanisms changed. We were on Heroku and about two years ago, we migrated everything to AWS, which gave us a lot more control, a lot more flexibility and the ability to scale, right?

And as we grew, we realized the systems that we had to build, the queuing servers, the scaling mechanisms changed. We were on Heroku and about two years ago, we migrated everything to AWS, which gave us a lot more control, a lot more flexibility and the ability to scale, right?

So again, with servers crashing every Friday and Saturday and the entire ops team being online trying to manage things, it was utter chaos. And now that seems like a distant story and people who joined us in news like, hey, how did you guys manage that? You have no idea. Actually, we have no idea either.

So again, with servers crashing every Friday and Saturday and the entire ops team being online trying to manage things, it was utter chaos. And now that seems like a distant story and people who joined us in news like, hey, how did you guys manage that? You have no idea. Actually, we have no idea either.

So again, with servers crashing every Friday and Saturday and the entire ops team being online trying to manage things, it was utter chaos. And now that seems like a distant story and people who joined us in news like, hey, how did you guys manage that? You have no idea. Actually, we have no idea either.

But yes, we've had to fight a lot in making sure as we grew from 10, 150,000 orders to a million orders that our service scaled. We learned in the process. We learned about peak times. We learned about cost management.

But yes, we've had to fight a lot in making sure as we grew from 10, 150,000 orders to a million orders that our service scaled. We learned in the process. We learned about peak times. We learned about cost management.

But yes, we've had to fight a lot in making sure as we grew from 10, 150,000 orders to a million orders that our service scaled. We learned in the process. We learned about peak times. We learned about cost management.

We've hired people with specialty in these domains because at the end of the day, what we've realized is we serve a very, not to be too self-wampus, but we serve a very critical role in this ecosystem. But if our servers go down, a lot of restaurants will lose their revenue and a lot of customers will not get their food. So that sense of responsibility does not escape us.

We've hired people with specialty in these domains because at the end of the day, what we've realized is we serve a very, not to be too self-wampus, but we serve a very critical role in this ecosystem. But if our servers go down, a lot of restaurants will lose their revenue and a lot of customers will not get their food. So that sense of responsibility does not escape us.

We've hired people with specialty in these domains because at the end of the day, what we've realized is we serve a very, not to be too self-wampus, but we serve a very critical role in this ecosystem. But if our servers go down, a lot of restaurants will lose their revenue and a lot of customers will not get their food. So that sense of responsibility does not escape us.

The team, by far, there's not even a second, a close second or third. We just went through a major rebranding right now. You've seen the movie Social Network, how there was this major moment where, hey, you should not be called the Facebook anymore. You should be just called Facebook, right? The joke is we made a similar change where we are not, it's a checkmate anymore.

The team, by far, there's not even a second, a close second or third. We just went through a major rebranding right now. You've seen the movie Social Network, how there was this major moment where, hey, you should not be called the Facebook anymore. You should be just called Facebook, right? The joke is we made a similar change where we are not, it's a checkmate anymore.

The team, by far, there's not even a second, a close second or third. We just went through a major rebranding right now. You've seen the movie Social Network, how there was this major moment where, hey, you should not be called the Facebook anymore. You should be just called Facebook, right? The joke is we made a similar change where we are not, it's a checkmate anymore.

We're just called checkmate. The entire rebranding happened because we realized that we now stand for a lot more than what we started out. We are not a technology company. We are a solutions oriented company that uses technology as a way to solve problems. How we solve problems is a combination of technology and service layer.

We're just called checkmate. The entire rebranding happened because we realized that we now stand for a lot more than what we started out. We are not a technology company. We are a solutions oriented company that uses technology as a way to solve problems. How we solve problems is a combination of technology and service layer.