Component-Based Rails Architectures are a great way to take advantage of microservices in Ruby...IF you know what you're doing.
The Dos and Don’ts of CBRAHow to break up the monolith
View Slide
The Dos and Don’ts of CBRAHow to break up the monolith (or not)
Who am I?Rails dev for 8+ years, @theadamconrad
What does CBRA mean?Component-Based Rails Architecture
What does CBRA mean?Use Rails::Engine to glue stuff together!
Rails::Engines
How do we know when to switch?
Dos of CBRAs
Dos of CBRAsThink: complexity
Dos of CBRAsThink: complexity1. You actually usemicroservices
Dos of CBRAsThink: complexity1. You actually usemicroservices2. Testing isolation
Dos of CBRAsThink: complexity1. You actually usemicroservices2. Testing isolation3. You know what you’redoing
Don’ts of CBRAs
Don’ts of CBRAsPretty much any other time
Don’ts of CBRAsPretty much any other time1. Lots of communicationbetween engines
Don’ts of CBRAsPretty much any other time1. Lots of communicationbetween engines2. Dependency hell
Don’ts of CBRAsPretty much any other time1. Lots of communicationbetween engines2. Dependency hell3. Because SOAs /Microservices are the“in thing”
Thanks!Find me @theadamconradhttps://userinterfacing.com/how-to-improve-on-naming-contexts-in-domain-driven-design/