Microservices in Your Datacenter
0 likes534 views
The document discusses the challenges and considerations in product engineering for microservices within a datacentre context at DigitalOcean. It highlights the importance of prioritizing rapid provisioning, monitoring, and application deployment while addressing common issues like duplicated code and event-driven architecture. The presentation also touches on the evolution of services such as billing and invoicing, advocating for efficiency and robustness in client libraries.
Microservices in Your Datacenter
- 7. Why am I even here?
- 8. Projects take too long idea $$
- 9. Upon closer look idea $$
- 11. We will be talking about Product Engineering
- 12. I am completely biased
- 13. "The general tendency is to over- design the second system, using all the ideas and frills that were cautiously sidetracked on the first one." — Fred Brooks, "The Second-System Effect"
- 15. Some stuff is just mandatory.
- 16. • Rapid provisioning • Basic Monitoring • Rapid application deployment
- 17. • Rapid provisioning 😎 • Basic Monitoring💩 • Rapid application deployment 💩
- 21. And some other stuff is just taste.
- 22. HTTP+JSON
- 23. Performance isn’t likely to be your problem using it.
- 24. Tolerant Reader leads to lots of duplicated code.
- 25. Duplicated code leads to client libraries.
- 26. Client libraries lead to release management overhead.
- 27. Client libraries lead to hidden business logic.
- 28. Client Libraries need to be efficient, lean, robust.
- 29. They don’t need to be written manually.
- 30. Something I’m sure you’ll have:
- 32. Event Bus Circles can often be broken by async events
- 33. We are event driven by nature
- 36. What should be a service?
- 37. billing
- 39. rating invoicing payment -collectingenabled -features Highly visible Not visible Novel Commodity
- 40. It’s early days, but we can already see progress. idea $$