Keynote - From Monolith to Microservices - Lessons Learned in the Real World
0 likes166 views
This document summarizes lessons learned from transitioning to a microservices architecture in the real world. It discusses doing the transition for the right reasons like scalability and agility rather than because microservices are cool. An evolution approach through breaking a monolith into services is compared to a revolution of rewriting a system. It also covers the importance of DevOps, organizational change, and overcoming the steep learning curve of new technologies in the transition. Microservices require governance and structure rather than anarchy. The essence of independent, scalable services must be understood to avoid recreating monolithic problems.
Keynote - From Monolith to Microservices - Lessons Learned in the Real World
- 2. From Monolith to Microservices: Lessons Learned in the Real World Alon Fliess Chief Software Architect [email protected] @alon_fliess https://alonfliess.me Eran Stiller Chief Technology Officer [email protected] @eranstiller https://stiller.blog
- 3. Agenda ▪ The Hype of Microservices ▪ Lessons Learned in the Real World ▪ Do It for the Rights Reasons ▪ Evolution or Revolution, That Is the Question! ▪ DevOps, Organizational Change & Culture Change ▪ Steep Technology Learning Curve ▪ No Anarchy ▪ Learn the Essence of What Is Microservices ▪ Q&A 7
- 4. About Us 8 Alon Fliess (@alon_fliess) ▪ Chief Architect & Founder - CodeValue & OzCode ▪ Microsoft Regional Director & Azure MVP ▪ Lead software analysis, architecture and design ▪ Lead analysis workshops Eran Stiller (@eranstiller) ▪ CTO & Founder at CodeValue ▪ Software architect, consultant and instructor ▪ Microsoft Regional Director & Azure MVP ▪ Founder of Azure Israel Meetup
- 5. The Hype of Microservices 9
- 6. 10
- 8. Micro Service Architecture ▪Some principles: ▪A micro service should be less then 100 lines of code ▪ 100 is just a number that emphasizes: small ▪ Usually can be developed in one scrum sprint ▪ It should be easy to understand, fast to deploy, and cheap to reimplement (throw the old one) ▪A micro service should be independently developed & deployed ▪A micro service should has private data ownership ▪Eventual Consistency ▪Versioning
- 9. MSA – Accessing Data Consistency PartitioningAvailability CAP Theorem
- 10. Eventual consistency “The value across all nodes will be consistent with the last update that was made -- eventually” The sunlight that you see indicates that the sun was still there eight minutes ago! ▪ When you see in a shopping site that a product is available, is it? ▪ Handling eventually consistency is not easy
- 11. The Hype of Microservices 15
- 12. Lessons Learned in the Real World 16
- 13. Lessons Learned in the Real World ▪ Do It for the Rights Reasons ▪ Evolution or Revolution, That Is the Question! ▪ DevOps, Organizational Change & Culture Change ▪ Steep Technology Learning Curve ▪ No Anarchy ▪ Learn the Essence of What Is Microservices 17
- 14. Lessons Learned in the Real World ▪ Do It for the Rights Reasons ▪ Evolution or Revolution, That Is the Question! ▪ DevOps, Organizational Change & Culture Change ▪ Steep Technology Learning Curve ▪ No Anarchy ▪ Learn the Essence of What Is Microservices 18
- 15. Why Move to Microservices? 19
- 16. Answer #1 – It’s Cool! 20
- 17. Answer #2 – It’s Easier/Faster 21
- 18. There is a Learning Curve… 22
- 19. Answer #3 - Scale 23
- 20. Answer #4 - Agility 24
- 21. Do It for the Right Reasons ▪ Don’t make the transition because: ▪ Microservices are cool ▪ Microservices are easier or faster to develop ▪ Do make the transition because: ▪ When done right, it can scale better ▪ When done right, it makes the development more agile 25
- 22. Lessons Learned in the Real World ▪ Do It for the Rights Reasons ▪ Evolution or Revolution, That Is the Question! ▪ DevOps, Organizational Change & Culture Change ▪ Steep Technology Learning Curve ▪ No Anarchy ▪ Learn the Essence of What Is Microservices 26
- 23. Evolution or Revolution, That Is the Question! 27 http://cdaworldhistory.wikidot.com/europe-faces-revolutionshttps://commons.wikimedia.org/wiki/File:Human_evolution.svg
- 24. Case Study – Breaking the Monolith (Evolution) 28 A large scale multitenant trading system
- 25. Case Study – Rewrite (Revolution) 29 https://www.flickr.com/photos/meyyappan_tirupur/9498661067 An old advanced 2D/3D CAD MFC based application
- 26. Lessons Learned in the Real World ▪ Do It for the Rights Reasons ▪ Evolution or Revolution, That Is the Question! ▪ DevOps, Organizational Change & Culture Change ▪ Steep Technology Learning Curve ▪ No Anarchy ▪ Learn the Essence of What Is Microservices 30
- 27. DevOps 31 If I have to give you one piece of advice, DevOps would be it.
- 28. What is DevOps? 32 Taken from https://commons.wikimedia.org/wiki/File:Devops-toolchain.svg
- 29. Main DevOps Practices Dev/Commit Unit-Tests Integration- Tests 33 Continuous Integration Dev/Commit Unit-Tests Integration- Tests Acceptance Tests Continuous Delivery Dev/Commit Unit-Tests Integration- Tests Acceptance Tests Production Continuous Deployment
- 30. How Agile is Agile? 34 Source: “Accelerate: State of DevOps 2018 Report” https://cloudplatformonline.com/2018-state-of-devops.html
- 31. Automation is King 35 Source: “Accelerate: State of DevOps 2018 Report” https://cloudplatformonline.com/2018-state-of-devops.html
- 32. Spend More Time on New Work 37 Source: “Accelerate: State of DevOps 2018 Report” https://cloudplatformonline.com/2018-state-of-devops.html
- 33. DevOps is Key 38 Source: “Accelerate: State of DevOps 2018 Report” https://cloudplatformonline.com/2018-state-of-devops.html
- 34. Lessons Learned in the Real World ▪ Do It for the Rights Reasons ▪ Evolution or Revolution, That Is the Question! ▪ DevOps, Organizational Change & Culture Change ▪ Steep Technology Learning Curve ▪ No Anarchy ▪ Learn the Essence of What Is Microservices 39
- 35. Steep Technology Learning Curve ▪ Microservices ≠ new programming language ▪ A .Net shop company wanted to move to node.js ▪ They’ve heard that this is the right way for MSA ▪ We convinced them to move to .NET Core ▪ They still needed to learn a lot: Architecture, Docker, K8S, … 40
- 36. Wind of Change ▪ Sometimes it is an opportunity ▪ If the new UI technology stack is a Web based, node.js in the service side makes sense ▪ Utilizing a better technology for a microservice is an advantage ▪ Conclusion: ▪ Do what is best to your organization culture ▪ Take into account that you must plan an education phase ▪ Moving to MSA is a chance to make some technological progress 41
- 37. Lessons Learned in the Real World ▪ Do It for the Rights Reasons ▪ Evolution or Revolution, That Is the Question! ▪ DevOps, Organizational Change & Culture Change ▪ Steep Technology Learning Curve ▪ No Anarchy ▪ Learn the Essence of What Is Microservices 42
- 38. Microservices Are NOT the Wild West… 43
- 39. Microservices Are NOT the Wild West… ▪ Common examples include: ▪ “Let’s just start and add services as required” ▪ “Services can arbitrarily call each other” ▪ “Let’s just throw the old code away” ▪ “The transition to Microservices is a strictly technical issue” 44
- 40. Microservices Need to be Governed ▪ Microservices, like Monoliths, start with good intentions ▪ Both become convoluted over time when not properly governed ▪ And then you’re back in square one, but this time with a distributed system 45
- 42. Lessons Learned in the Real World ▪ Do It for the Rights Reasons ▪ Evolution or Revolution, That Is the Question! ▪ DevOps, Organizational Change & Culture Change ▪ Steep Technology Learning Curve ▪ No Anarchy ▪ Learn the Essence of What Is Microservices 47
- 43. Learn the Essence of What Is Microservices ▪ A new system that is based on an MSA ▪ Many small services that ▪ Use Kafka to path messages ▪ the message schema is shared among the services ▪ A single DB schema served all microservices ▪ Use k8s to host and monitor single service instances for robustness ▪ The result – The Microservice monolith ▪ Apply a fix: ▪ Break the shared schema to each service and use versioning ▪ Break the DB to many DBs ▪ Remove the state from the service to allow many instances ▪ Decide when it is right to use Kafka and when other mechanisms are preferred 48
- 44. Summary 49
- 45. MSA – The hype and the reasons ▪ It’s a fashion, it’s the future, it’s cool!!! ▪ It’s software engineering’s ultimate goal ▪ Low Coupling and High Cohesion for free !? ▪ We all want to: ▪ Develop in a faster cadence ▪ Deploy any feature as soon as its finished ▪ Have the ability to immediately rollback ▪ Have versioning independent code ▪ Have abilities to monitor our system and conduct a canary or A-B testing ▪ But does it is really come for free? 50
- 46. Takeaways ▪ MSA – extreme low coupling and high cohesion ▪ With cost and responsibility ▪ Do it right or don’t ▪ Use infrastructure and tools ▪ Decide whether to migrate (evolution) or restart (revolution) ▪ Consider the learning curve ▪ Architecture, technology, DevOps ▪ It is not just a technology change – it is a major culture change ▪ Goes very well with the agile methodology 51
- 47. Takeaways 52
- 48. Alon Fliess Chief Software Architect [email protected] @alon_fliess http://alonfliess.me Eran Stiller Chief Technology Officer [email protected] @eranstiller https://stiller.blog