The Dos and Don'ts of CBRA

The Dos and Don'ts of CBRA

Component-Based Rails Architectures are a great way to take advantage of microservices in Ruby...IF you know what you're doing.

43e0fc25bbcc4a1bcf1e6139e424ee35?s=128

Adam Conrad

July 10, 2018
Tweet

Transcript

  1. The Dos and Don’ts of CBRA How to break up

    the monolith
  2. The Dos and Don’ts of CBRA How to break up

    the monolith (or not)
  3. Who am I? Rails dev for 8+ years, @theadamconrad

  4. What does CBRA mean? Component-Based Rails Architecture

  5. What does CBRA mean? Use Rails::Engine to glue stuff together!

  6. None
  7. None
  8. Rails::Engines

  9. How do we know when to switch?

  10. Dos of CBRAs

  11. Dos of CBRAs Think: complexity

  12. Dos of CBRAs Think: complexity 1. You actually use microservices

  13. Dos of CBRAs Think: complexity 1. You actually use microservices

    2. Testing isolation
  14. Dos of CBRAs Think: complexity 1. You actually use microservices

    2. Testing isolation 3. You know what you’re doing
  15. Don’ts of CBRAs

  16. Don’ts of CBRAs Pretty much any other time

  17. Don’ts of CBRAs Pretty much any other time 1. Lots

    of communication between engines
  18. Don’ts of CBRAs Pretty much any other time 1. Lots

    of communication between engines 2. Dependency hell
  19. 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”
  20. Thanks! Find me @theadamconrad https://userinterfacing.com/how-to-improve-on-naming-contexts-in-domain-driven-design/