Downloaded 80 times
Uploaded byEberhard Wolff
Microservices and Self-contained System to Scale Agile
The document discusses microservices and self-contained systems as approaches to scaling agile development, emphasizing independent deployment units and reducing dependencies. It outlines the architecture's benefits, such as improved robustness, faster feedback, and the ability to handle legacy systems more efficiently. The author advocates for using these methods in large projects to enhance sustainable development and continuous delivery.
More Related Content
![[WSO2Con Asia 2014] Accelerating Mobile App Development with MBaaS](https://cdn.slidesharecdn.com/ss_thumbnails/mbaas-wso2conasia-2014-140325234640-phpapp02-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to Microservices and Self-contained System to Scale Agile
Microservices and Self-contained System to Scale Agile
- 1. Microservices & Self- ContainedSystems to Scale Agile Eberhard Wolff Fellow, innoQ @ewolff
- 2.
- 3.
- 4.
- 5.
- 6. Server Server Microservices: Definition > Independentdeployment units > E.g. process, VMs, Docker containers > Any technology > Any infrastructure Micro Service Micro Service
- 7.
- 8. Layered Microservices iOS AndroidWeb Order Search Catalog BillingCustomer Backend Backend Backend
- 9. Layered Microservices > ReusableBackend Services > Mobile client / Web App as frontend > Backend for frontend (BFF): Custom backend services > ...to implement frontend specific logic
- 10. Layered: Issues > BFFmight contain the same logic – same processes > BFF might contain most relevant logic > Change to a business process means changing many services > Lots of communication
- 11.
- 12. Deployment monolith Graphics by RomanStranghöhner, innoQ http://scs-architecture.org
- 13.
- 14. … wrap domainin separate web application …
- 15.
- 16. SCS = user interface+ businesslogic+ data storage
- 17. Each SCS containsall layers.
- 18. Self-contained Systems should be integrated inthe web interface
- 19. Synchronous remote calls insidethe business logic should be avoided.
- 20. Asynchronous Remote calls reduce dependenciesand prevent error cascades.
- 21. Every SCS bringsits own data storage with its own (potentially redundant) data
- 22. Domained scoped SCS enablesthe development, operation and maintenance of an domain by a single team. Team 1 Team 2 Team 3
- 23. 1 SCS = 1Domain = 1 Web App = 1 Team = 1-n Microservices
- 24. Why create sucha complex system?
- 25.
- 26. HTTP New Stuff Links No legacy code Anytechnology J Small code base
- 27.
- 28. Monoliths > Architecture rot >…not maintainable any more > …and can’t be rewritten / replaced
- 29. Microservices > Distributed systemof small units > Architecture violations harder > Architecture won’t rot > Small units > Easy to replace > Service rotten? Replace!
- 30. Robust > One failingMicroservice doesn’t crash the system > However, Microservices must deal with failing Microservices
- 31.
- 32. Principles behind the AgileManifesto Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
- 33.
- 34.
- 35. Build Pipeline: Problems > Complexinfrastructure > Huge database > 3rd party integration > Slow feedback > Test everything for each commit > Huge deployment unit > Deployment slow
- 36.
- 37.
- 38.
- 39. Build Pipeline for Microservices >Independent deployment > Build pipeline per Microservice > Smaller > Easier to set up > Less features (3rd party systems) > Faster Feedback: Less tests
- 40. Independent Scaling > Canscale each Microservice indenpendently > Much easier than for a Deployment Monolith
- 41. Technology Freedom > Nomeetings for introducing a bug fix in a library! > No big migration away from outdated technology > Easier experiments > Higher motivation
- 42.
- 43. Scaling Agility > Domore > Get more stories implemented > ...and running in production TODO IN PROGRESS DONE
- 44. Scaling Agility > Addmore people > Let the work in parallel > Build more teams
- 45. What is theproblem?
- 46. Communication > Agile meanscommunication > Instead of written requirements > ...story cards > + direct communication
- 47. # Persons vs. PotentialLinks 0 100 200 300 0 10 20 30
- 48. Communication is great! Needmore persons
- 49. Challenges for Scaling Agile >Dependencies cause delays > Too much communication about functionalities,... > ...releasing software, > ...and technologies
- 50. Challenges for Scaling Agile >Dependencies cause delays > Too much communication about functionalities... > ...releasing software, > ...and technologies
- 51. Conway‘s Law Architecture copies communication structures ofthe organization
- 52.
- 53. time DB Team Sprint Logic Team Sprint GUI TeamSprint 3 sprints
- 54. Domained scoped SCS enablesthe development of a domain by a single team – no coordination Order Team = UI+Logic+Database
- 55. Challenges for Scaling Agile >Dependencies cause delays > Too much communication about functionalities... > ...releasing software, > ...and technologies
- 56.
- 57.
- 58. Technical decisions can bemade independently from other systems (programming language, frameworks, tooling, platform)
- 59.
- 60. Why Microservices/SCS? Sustainable development speed ContinuousDelivery Choose best technology for job! Handle Legacy more efficient Independent Scaling Robustness Scaling Agile
- 61.
- 62. Conclusion: SCS & Microservices >Microservices have many advantages > SCS are a way to use Microservices > …for large projects > …to scale agile
- 63.
- 64. EMail [email protected] toget: Slides + Microservices Primer + Sample Microservices Book + Sample of Continuous Delivery Book Powered by Amazon Lambda & Microservices