While Rails provides us a great platform for rapid application development it doesn't give us much guidance on where to start placing common abstractions once our domain complexity grows. This talk isn't about the 'architecture astronaut' or fighting rails to implement 'better' patterns, it's a really basic intro to some of the layers you can implement tomorrow to compartmentalise your code without having to fight the framework.
YOU MAY ALSO LIKE:
- The JVM as a platform for building smart contracts (in London on 28th June 2017)
- Are You Managing or Leading? (in London on 4th July 2017)
- Masterclass: Reducing Technical Debt with Michael C. Feathers (in London on 21st - 22nd August 2017)
- µCon 2017: The Microservices Conference (in London on 6th - 7th November 2017)
Where does my code go?
Michael is a developer working on mobile payments platforms at mGage where he's fortunate enough to see both: the downsides of a lack of application structure (an ancient, close to unmaintainable merb monolith); as well as how simple it can be to make changes in systems where we think of clean and compartmentalised architectures (our shiny new(ish) platforms to replace the monolith).