The idea was to have clients (web, iOS, and Android) login using the new service, but still give them access to the monolith Grubhub APIs for search, menus, checkout, payments, and everything else. To start, we built a routing layer and a diner registration, authentication, and access control service. Again, we decided to start with a few core pieces of the platform and migrate all of the consumer Seamless users over to a mix of the new platform and the Grubhub platform. It would be inconceivable to move to a new platform in one go. When I first started at Grubhub, I remember being very impressed at the depth and breadth of complexity involved in taking and fulfilling an online order. At the same time, we had the foresight to spend effort designing and building a platform for the future - a distributed, scalable, and fault-tolerant platform in the cloud. The old Grubhub platform’s days were numbered, too. Instead of pouring more money into two separate platforms, we decided to sunset the legacy Seamless software stack and migrate to the Grubhub stack. We had a graph we called the “Doomsday Graph,” which predicted the date - our doomsday - when the Microsoft SQL server powering it all would no longer sustain the projected traffic and order growth. The Seamless platform had been around longer and definitely showed its age. Both of them were monoliths running separate sets of data, each out of a single data center. Diner accounts, restaurant accounts, financial reporting, restaurant tablets, and everything in-between had a separate implementation in the respective platforms.

When the two companies merged, their technology was running on two completely independent platforms. Our first major migration was following the merger of Seamless and Grubhub. So getting the data migration right is really important.īut it wasn’t always so easy. Users hate change - any change, even if it is demonstrably better. It’s important to convert it accurately, in order to not make your users angry in this conversion. We were lucky to have a lot of past experience to draw on when we planned these recent migrations of large amounts of diner data. In the past year, we’ve migrated tens of thousands of diners from Eat24, Foodler, and OrderUp onto our platforms. Data migration strategies for making a “Seamless” transition

Seamless grubhub merger