RR 371: The Modular Monolith: Rails Architecture with Dan Manges

Panel: David RichardsDave KimuraCatherine Meyers Special Guests: Dan MangesIn this episode of Ruby Rogues, the panel talks to Dan Manges about his blog post entitled The Modular Monolith: Rails Architecture. Dan is the CTO of Root, which is a car insurance carrier in Columbus, Ohio. They started the company a few years ago because they felt that the prices people pay for car insurance should be based primarily on diving behavior and not demographics. They talk about how he built the architecture of the app for his company, what a Modular Monolith is, their different gems, and more!In particular, we dive pretty deep on:Dan introCTO and Co-Founder of RootTracking driving habits of users to determine rateRuby on RailsArchitecture of the appBack-end platform in RailsMobile as the primary interfaceSee the app in the Google Play and iTunes storesCurrent direction for the companyIdentify good architectural boundaries in the code baseMonolithsWhat is Modular Monolith?Why did you decide not to go the microservices route?Microservices introduce tradeoffs in your efficiency of making changesNot having a too fragmented back-end platformDo you have one large schema?Maintaining productivityEnginesSeparate integration testsIntegration tests between various componentsTheir rating engineDeploymentsHis article: The Modular Monolith: Rails ArchitectureHighly recommends their modular monolithEverything is in one codebaseAnd much, much more!Links:The Modular Monolith: Rails ArchitectureRootRuby on RailsRoot in the Google Play storeRoot in iTunesdan-manges.com@dan_mangesDan’s MediumDan’s GitHubSponsors