Monday 17th October, 2016
1:00pm to 1:40pm
You’re building a new Rails App… do you go with a single large “monolith”, break it up into smaller micro-services, or try to find the happy balance between them? Does it matter if you’re on a small team at a start-up vs. a large company with hundreds of developers?
This talk is about organizing your code, putting in a little work now to define clear boundaries between your app’s components, whether it’s in a single app or multiple services.
We’ll look at some practical examples and techniques to make transitioning from monolith to micro-services as easy as possible. The examples will be in Rails, but the principles can be used for any backend.
Sign in to add slides, notes or videos to this session