Connecting microservices allows companies to be scalable and bring about the flexibility that partners want. We maintain application programming interfaces (APIs) that allow external companies to connect with us, while ensuring that end customers get the same service no matter whether the product is internal or external.
The Fun with Flags feature flagging service helps Product & Tech teams at Delivery Hero make their release flow safer and less stressful. By allowing them to serve features to random or specific segments of their users, it also facilitates experimentation for data-driven product decisions.
In Talabat we have a big monolithic application written in .Net using MS SQL database with a single read node. With continuous growth in traffic and number of users, we are facing issues in terms of performance, scalability and robustness. We have bottlenecks when it comes to releases; independent release of features is a pain. Moving forward, Microservices seems to be a clear solution for our problems.
In this article I will explain the approach Talabat used to design microservices and move to AWS at the same time. This might not work for everyone but for Talabat, it looks very promising.
Daniel McLaine is a Product Manager for the Global Product Team at Delivery Hero. Over the next few months, he will regularly provide insights on how we are creating a culture of experimentation at Delivery Hero. The first installment with Daniel focuses on how the idea originated and the challenges he faced along the way.
As mentioned in the previous article, Salesforce is a core platform at Delivery Hero to manage and acquire partnering restaurants. Since we are operating across the globe in more than 40 countries, we are facing various challenges especially concerning the restaurant location in Salesforce.