Download as PDF, PPTX
Uploaded bymichele franzin
Come ti smantello un'app monolitica in microservices
The document discusses the challenges and methodologies for disassembling a monolithic application into microservices. It outlines the characteristics of monolithic and microservice architectures, emphasizing the benefits of microservices such as improved fault isolation and independent deployment, while also addressing the complexities introduced by distributed systems. The author shares strategic steps for decomposition, highlights the importance of communication, and advocates for initially adopting a monolithic approach before transitioning to microservices.
More Related Content
Similar to Come ti smantello un'app monolitica in microservices
Come ti smantello un'app monolitica in microservices
- 1. HOW TO DISASSEMBLE AMONOLITHIC APP IN (NOT-SO)MICRO-SERVICES Turin - 17 november 2015
- 2.
- 4.
- 5.
- 6. DISCLAIMER my personal opinion peoplehave different experiences ideas, comment, etc contact me @realfuzzy subject is wide, so I’d love to hear your thoughts :-) It’s not a code talk (but I’ll show you some code)
- 7. AGENDA:THERE’S NO AGENDA I’ve gota tale instead
- 12. BUAHAHAHAHA! I AM THE MONOLITH! COMETO THE WORLD TO BRING IMMOBILISM AND COMPLEXITY!
- 14. MONOLITHIC MICROSERVICE architecture isthe keyword ARCHITECTURE ARCHITECTURE
- 15.
- 16. THE (SOMETIMES EVIL)MONOLITH http://www.infoq.com/articles/microservices-intro
- 17. ✓simple to develop ✓IDEs& development tools support ✓easy to test ✓simple to deploy ✓works well for relatively small apps
- 18. - growth overloadseverything - difficult to adopt new technologies - often stuck with the starting choices - doesn’t scale to long-lived-application
- 19.
- 20. WHAT’S A MICROSERVICE •suite of small services • running in its own process • communicating with lightweight mechanisms • built around business capabilities • independently automated deployable • minimum of centralized management • technology agnostic
- 21.
- 22. ✓each microservice isrelatively small ✓easier for a developer to understand ✓easier to scale development ✓improve fault isolation ✓develop and deploy independently ✓no long-term commitment to a tech-stack ✓allow a fine-grained performance tuning or scaling
- 23. - additional complexityof a distributed system - tools/IDEs are monolithic applications oriented - testing is more difficult - must implement the inter-service communication - increase memory consumption
- 24.
- 25. GOALS ‣ time ‣ budget ‣shit (can) happens ‣ ship
- 26. AGENDA* ✓ what’s amicroservice? • why have I to jump in ? • where I can start from ? • how I should be aware of ? * I know, I know, I lied about the agenda
- 28. Sir. Tools A warriorthat can use every kind of tool as a weapon Strateky Sensei Master renowned for its strategic and tactical ability Workodoo Master The work-force is strong with this one
- 31. HAHAHAHA! YOUR EFFORTS ARE NOT ENOUGHTO DEFEAT ME!
- 33. Your efforts havelittle effect! an orthogonal approach might help you ...
- 35. Q0: HOW TODECOMPOSE A MONOLITH? 1. Identify business boundaries 2. start decomposing each into own microservice 3. follow the Single Responsibility Principle 4. goto :2
- 36.
- 37.
- 38. CHOOSE WISELY • Reliability •Routing algorithms • Highly Availability • Supported protocols
- 39.
- 40. OUR CHOICE ☛RABBITMQ • AMPQ message broker • Erlang • Fast, reliable, secure • Many clients • Commercial support
- 41. SPECIFICATION IS A MUSTHAVE (no matter what)
- 42. DESIGN FOR FAILURE aka:communicate when communication is hard
- 43.
- 44.
- 45. SLIM FIT circuit_breaker https://github.com/ wsargent/circuit_breaker breaker_boxhttps://github.com/ sittercity/breaker_box CB2 https://github.com/pedro/cb2 S M L
- 46.
- 47. –Giovanni Mela “Inserisci quiuna citazione”. 9XL
- 48. – Martin Fowler,Chief Scientist -ThoughtWorks “…don’t even consider microservices unless you have a system that's too complex to manage as a monolith”
- 49.
- 50.
- 54. –Giovanni Mela “Inserisci quiuna citazione”.
- 58. – Melvin Conway,1968 “organizations which design systems … are constrained to produce designs which are copies of the communication structures of these organizations”
- 59.
- 60. – Martin Fowler,Chief Scientist -ThoughtWorks “For many people throwing away a code base is a sign of failure, perhaps understandable …, but still failure.”
- 61.
- 62. POLYGLOT IS NICE butmother tongue is fair enough
- 63. DEVOPS! no devops?!? noparty. https://www.flickr.com/photos/91657289@N02/10218392744
- 64. The Smith Master craftsman expertin forging anything The Sculptor An artist able to give shape to magnificent works The Painter Colors and shapes come to life on her canvas!
- 72. NO MONOLITHS WERE HARMEDINTHE MAKING OFTHIS PRESENTATION
- 73.
- 74. TAKEAWAYS • go monolithfirst • communication (all-around) is strategic assets • start simple, don’t fear the change • take decisions. I-really-mean-that.
- 75. …WHAT’S NEXT ? •testing • CQRS + ES • log analisys & monitoring • metrics • …
- 76.