Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Rubyslava beyond the_monolith

319 views

Published on

So, your monolith is getting out hand and you read about this cool microservice infrastructure thing. You may have done something similar, but are not quite sure whether to take the plunge or not.

Published in: Software
  • Be the first to comment

  • Be the first to like this

Rubyslava beyond the_monolith

  1. 1. Beyond the monolith @michalolah
  2. 2. About • Crealytics - Camato • Why services? • The good • The bad • Tips
  3. 3. Crealytics - Camato http://www.camato.de/en/start.html
  4. 4. Adwords
  5. 5. Adwords
  6. 6. Crealytics - Camato
  7. 7. Current Infrastructure • Camato + 3 services (CAP) + 3 on the way • 5+ services (CDA) • 100+ VMs
  8. 8. Why services?
  9. 9. Cognitive overhead
  10. 10. Slow app/tests
  11. 11. Cannot upgrade anything
  12. 12. The good
  13. 13. Firm Boundaries a.k.a. ‘Let me leak this abstraction just a little’
  14. 14. Language does not matter
  15. 15. Fast tests
  16. 16. Clear ownership
  17. 17. The bad
  18. 18. No good way to integration test
  19. 19. Considerable overhead
  20. 20. Tips
  21. 21. Manage your service explosion • If possible use REST JSON • Don’t create a service per idea • Infrastructure • Monitoring • Client gems/libraries • Have configuration conventions
  22. 22. Carefull about split brain
  23. 23. Large data • Think millions of rows • Forget JSON • CSV is your friend
  24. 24. Use docker • At least to run tests • Eliminates ‘works on my machine’
  25. 25. Automate build/deployment • Use service (codeship, travis, snapci) • Roll your own (jenkins)
  26. 26. Should I do it? • You need to be big enough • DO NOT start out this way
  27. 27. Thank you Questions?

×