Microservices
•Download as PPTX, PDF•
1 like•471 views
This document discusses moving from a monolithic architecture to microservices. It notes some advantages of microservices like improved tools, language and library usage, and faster deployment times. However, it cautions against simply following "microservices mantras" and stresses the importance of being ready to receive attacks rather than relying on the likelihood they won't occur. Microservices should share nothing and start independently, but still aim for high availability and responsiveness as a system. The document provides additional reading resources on monoliths, microservices, and systems thinking.
Report
Share
Microservices
- 4. Monolith
- 6. Artur Caliendo Prado artur.prado@youse.com.br @artur.prado @artur_caliendo@arturcp
- 7. Do not simply follow the mantra
- 11. Why not a monolith? Tools Language Process Time to deploy Libraries
- 13. Microservices
- 15. Share “nothing”
- 26. "Rely not on the likelihood of the enemy's not coming, but on our own readiness to receive him; not on the chance of his not attacking, but rather on the fact that we have made our position unassailable" The art of war, Sun Tzu.
- 33. "No man is an island, Entire of itself, Every man is a piece of the continent, A part of the main." John Donne "One Microservice is no Microservice — they come in systems."