Rubyslava beyond the_monolith
0 likes•452 views
The document discusses the challenges and advantages of using a microservices architecture within the context of Crealytics and Camato. It highlights issues like cognitive overhead, integration testing difficulties, and the importance of monitoring and automation, while providing tips for managing service proliferation. Additionally, it advises against adopting this architecture without sufficient scale and suggests best practices for implementation.
Rubyslava beyond the_monolith
- 2. About • Crealytics - Camato • Why services? • The good • The bad • Tips
- 4. Adwords
- 5. Adwords
- 7. Current Infrastructure • Camato + 3 services (CAP) + 3 on the way • 5+ services (CDA) • 100+ VMs
- 10. Slow app/tests
- 12. The good
- 13. Firm Boundaries a.k.a. ‘Let me leak this abstraction just a little’
- 15. Fast tests
- 16. Clear ownership
- 17. The bad
- 18. No good way to integration test
- 20. Tips
- 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
- 23. Large data • Think millions of rows • Forget JSON • CSV is your friend
- 24. Use docker • At least to run tests • Eliminates ‘works on my machine’
- 25. Automate build/deployment • Use service (codeship, travis, snapci) • Roll your own (jenkins)
- 26. Should I do it? • You need to be big enough • DO NOT start out this way