Refactoring Legacy Apps with APIs and Messages

on YouTube ↗32m

" summary

A concrete plan: split the Rails monolith into small apps wired by internal HTTP APIs and an async message bus, move persistence and auth into separate services, and treat persistence as a service consumed by listeners. Practical tools mentioned include engines, Code Climate, Draper/Presenters, Faceted, Heroku, Postgres and optional Mongo or Node consumers. One codebase had a 2000+ message user model which yielded only an API with 12 methods when extracted; teams built a persistence API reporting API messaging API and shipped a sales dashboard in hours that raised conversion.

AI-written summary · about

" chapters (20)

1. 0:00Intro
2. 0:37Architecture
3. 2:07Big Out Front Design
4. 3:03Ad hoc Architecture
5. 6:12How did we get here
6. 7:56hexagonal design
7. 10:54APIs and messages
8. 13:08Objectoriented design
9. 15:48Legacy applications
10. 20:39Synchronicity
11. 21:46Presenter Pattern
12. 25:04Benefits
13. 25:40Autonomy
14. 26:49Downtime
15. 27:53True TDD
16. 28:16Btesting
17. 29:44Flexibility
18. 30:13democratization of architecture
19. 31:00conclusion
20. 31:18Outro

" related talks

• 27mScaling a Rails Monolith w/Event Driven MicroservicesMarko Anastasov · WindyCityRails 2016
• 20mSafely Decomposing a Highly Available Rails AppAdam Forsyth · Rocky Mountain Ruby 2015
• 40mService Architectures for Mere MortalsJamie Gaskins · RailsConf 2019
• 37mArchitecture: The Next GenerationTaylor Jones · RailsConf 2017
• 41mOff the Tracks - Challenging the Rails MindsetNick Sutterer · RubyConf AU 2013
• 36mWorking Compassionately with Legacy CodeAmar Shah · RubyConf 2015
• 23mAbstracting a Service - A Case Study in Forward Thinking with SOAStuart Corbishley · Rubyfuza 2013
• 34mSOA and the Monolithic Rails App Anti-PatternChris Wyckoff · MountainWest RubyConf 2011