Groupon recently completed a year-long project to migrate its U.S. web traffic from a monolithic Ruby on Rails application to a new multi-application stack with substantial results.
Groupon’s entire U.S. web frontend had been a single Rails codebase from its inception in 2008. The frontend codebase quickly grew large, which made it difficult to maintain and challenging to ship new
features. As a solution to this gigantic monolith, we decided to re-architect the frontend by splitting it into small, independent and more manageable pieces. At the center of this project, we rebuilt each
major section of the website as an independent application. We also rebuilt the infrastructure to make all the independent apps work together. Interaction Tier (I-Tier) was the result.
Learn about how Groupon achieved this great architecture migration and the business results it is driving.
14. business was stuck
4 could not build features fast enough
4 wanted to build features worldwide
4 mobile and web lacked feature parity
4 could not change look and feel
42. layout service options
4 distribute layout as library
4 use ESIs for top/bottom of page
4 apps are called through a “chrome
service”
4 fetch templates from service
43. layout service
chose a service
4 independent rollouts
4 changes can be shipped without
redploying all apps
4 easy to use in development
44. layout service
4 Uses semantic versioning
4 Roll forward with bug fixes
4 Stay locked on a specific version
4 Enable Site-Wide Experiments