The Dos and Don’ts of CBRA
How to break up the monolith
Slide 2
Slide 2 text
The Dos and Don’ts of CBRA
How to break up the monolith (or not)
Slide 3
Slide 3 text
Who am I?
Rails dev for 8+ years, @theadamconrad
Slide 4
Slide 4 text
What does CBRA mean?
Component-Based Rails Architecture
Slide 5
Slide 5 text
What does CBRA mean?
Use Rails::Engine to glue stuff together!
Slide 6
Slide 6 text
No content
Slide 7
Slide 7 text
No content
Slide 8
Slide 8 text
Rails::Engines
Slide 9
Slide 9 text
How do we know when to switch?
Slide 10
Slide 10 text
Dos of CBRAs
Slide 11
Slide 11 text
Dos of CBRAs
Think: complexity
Slide 12
Slide 12 text
Dos of CBRAs
Think: complexity
1. You actually use
microservices
Slide 13
Slide 13 text
Dos of CBRAs
Think: complexity
1. You actually use
microservices
2. Testing isolation
Slide 14
Slide 14 text
Dos of CBRAs
Think: complexity
1. You actually use
microservices
2. Testing isolation
3. You know what you’re
doing
Slide 15
Slide 15 text
Don’ts of CBRAs
Slide 16
Slide 16 text
Don’ts of CBRAs
Pretty much any other time
Slide 17
Slide 17 text
Don’ts of CBRAs
Pretty much any other time
1. Lots of communication
between engines
Slide 18
Slide 18 text
Don’ts of CBRAs
Pretty much any other time
1. Lots of communication
between engines
2. Dependency hell
Slide 19
Slide 19 text
Don’ts of CBRAs
Pretty much any other time
1. Lots of communication
between engines
2. Dependency hell
3. Because SOAs /
Microservices are the
“in thing”
Slide 20
Slide 20 text
Thanks!
Find me @theadamconrad
https://userinterfacing.com/how-to-improve-on-naming-contexts-in-domain-driven-design/