Micro Services - Neither Micro Nor Service
•
8 likes•3,716 views
Micro Services are a new approach to software architecture. This presentation discusses how small they should be - and wether they are really service - in the SOA sense.
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (7)
Similar to Micro Services - Neither Micro Nor Service
Similar to Micro Services - Neither Micro Nor Service (20)
More from Eberhard Wolff
More from Eberhard Wolff (20)
Recently uploaded
Recently uploaded (20)
Micro Services - Neither Micro Nor Service
- 1. Micro Services Neither Micro nor Service? Eberhard Wolff Freelancer Head Technology Advisory Board adesso AG http://ewolff.com
- 2. Architecture of Enterprise Java Apps Eberhard Wolff - @ewolff
- 3. Eberhard Wolff - @ewolff
- 4. Eberhard Wolff - @ewolff
- 5. How can I implement a new feature??? Eberhard Wolff - @ewolff
- 6. Eberhard Wolff - @ewolff L
- 7. ECommerce System Eberhard Wolff - @ewolff New Stuff Spring & OSGi
- 8. ECommerce System Eberhard Wolff - @ewolff New Stuff NSepwri nSgtu &ff OSGi
- 9. Eberhard Wolff - @ewolff HTTP New Stuff Links No legacy code Any technology J Small code base
- 10. Little programs are delightful to write in isolation, but the process of maintaining large-scale software is always miserable. Jaron Lanier
- 11. Friedenspreis des deutschen Buchhandels
- 12. Micro Services: Definition • Small • Independent deployment units • i.e. processes Eberhard Wolff - @ewolff • Any technology • Any infrastructure Micro Service Server Micro Service Server
- 13. Components Collaborate Eberhard Wolff - @ewolff Micro Service Micro Service Link REST Messaging Data Replication
- 14. Why Micro Services? • Strong modularization • Small deployment units • Faster & easier deployment • Continuous Delivery • Less risk in deployment • Choose best technology for each service Eberhard Wolff - @ewolff
- 15. Micro Service Eberhard Wolff - @ewolff = Micro?
- 16. Smaller modules 10-100LOC http://yobriefca.se/blog/ 2013/04/28/micro-service-architecture/ Eberhard Wolff - @ewolff =better
- 17. Smaller modules 10-100LOC http://yobriefca.se/blog/ 2013/04/28/micro-service-architecture/ Eberhard Wolff - @ewolff =better
- 18. Eberhard Wolff - @ewolff Game of Life
- 19. Game of Life in one line of APL life←{ ⍝ John Conway's "Game of Life". ↑1 ⍵∨.∧3 4=+/,¯1 0 1∘.⊖¯1 0 1∘.⌽⊂⍵ ⍝ Expression for next generation. } LOC is really a bad metric dyalog.com Eberhard Wolff - @ewolff
- 20. Eberhard Wolff - @ewolff Larger? • Micro Services have an overhead • Build & deployment pipeline • Version control
- 21. 1st Law of Distributed Objects • Don’t Distribute Your Objects! • Too much remote communication & overhead • Lesson learned from CORBA etc • http://martinfowler.com/bliki/ FirstLaw.html Eberhard Wolff - @ewolff
- 22. Latency Round Trip: 0,2-0,5 ms = 600.000-1.500.000 instructions@3GHz Eberhard Wolff - @ewolff Request Response Processing
- 23. 1st Law of Distributed Objects & Micro Services • Small Micro Services mean a lot of communication • Violate the 1st Law • Seems to work, though • http://martinfowler.com/articles/ distributed-objects-microservices. Eberhard Wolff - @ewolff html
- 24. Too small = too much communication Eberhard Wolff - @ewolff
- 25. Eberhard Wolff - @ewolff L
- 26. Again: Why Micro Services? Eberhard Wolff - @ewolff
- 27. The main reason Eberhard Wolff - @ewolff
- 28. How to scale Eberhard Wolff - @ewolff agile? Implement more feature
- 29. Eberhard Wolff - @ewolff Conways Law Architecture copies communication structures of the organization
- 30. Conway’s Law as a Limit • Won’t be able to create an architecture different from your organization • I.e. mobile, GUI & database team • Three technical artifacts Eberhard Wolff - @ewolff
- 31. Conway’s Law as an Enabler • Desired architecture = project structure • Team for each Micro Service • Team should be responsible for meaningful features • Ideal: Independent features Eberhard Wolff - @ewolff
- 32. On team can build and deploy features Eberhard Wolff - @ewolff – independently!
- 33. Micro Services must provide a sensible set of functionality Eberhard Wolff - @ewolff
- 34. Conway’s Law & Size • Upper limit: What a (small) team can handle • …and a meaningful set of features • Probably not too small • Lower limit: Depends on overhead / technology Eberhard Wolff - @ewolff
- 35. Micro Service = Micro? • Size doesn’t matter too much • Teams must be able to work independently • Small enough for one team • Not too much overhead Eberhard Wolff - @ewolff
- 36. Micro Service Eberhard Wolff - @ewolff = Service?
- 37. Micro Services Eberhard Wolff - @ewolff = SOA?
- 38. Service? unassociated loosely coupled units of functionality that are self-contained (Wikipedia, SOA) Eberhard Wolff - @ewolff
- 39. Portal / Web Service Service Service Service Eberhard Wolff - @ewolff SOA Service Service Service Service Integration CRM Order
- 40. Eberhard Wolff - @ewolff SOA • Enterprise wide effort • Services provided by different organizational units • Large monolithic deployments • …offer multiple services • Enterprise-wide integration • Portal / Web as universal GUI for all services
- 41. Eberhard Wolff - @ewolff SOA Service • Just one interface of a large monolith • No GUI • Different projects for different services
- 42. Micro Services CRM Eberhard Wolff - @ewolff Forecast Reporting Mass EMailing Web Tracking Integration
- 43. SOA vs. Micro Services Eberhard Wolff - @ewolff • Technology: Similar • i.e. integration • But: Smaller deployment units
- 44. Micro Services just structure the application Like JARs etc. Eberhard Wolff - @ewolff
- 45. GUI for Micro Services • Meaningful features will need a GUI • Customer talks to one team for GUI & logic • Less communication • 1st Law of Distributed Objects Eberhard Wolff - @ewolff
- 46. Micro Services Eberhard Wolff - @ewolff SOA • Enterprise wide effort • Services provided by different organizational units • Large monolithic deployments • …offer multiple services • Just one project • Services provided by one team • Small deployments • …offer one service each
- 47. Micro Services Eberhard Wolff - @ewolff SOA • Enterprise wide integration • Portal / Web as universal GUI for all services • Just one project • Each component has its own GUI
- 48. Conclusion Eberhard Wolff - @ewolff
- 49. Conclusion: Micro Services • Micro Services are a new way of modularization • More technological freedom • Easier, faster and less risky deployment Eberhard Wolff - @ewolff
- 50. Conclusion: Micro Eberhard Wolff - @ewolff • Size not too important • Meaningful set of features • Smaller than SOA services
- 51. Conclusion: Service • Modules of an application • Include GUI • Provide not just an interface to call Eberhard Wolff - @ewolff • Structure one project • …not the Enterprise IT
- 52. Thank You! Eberhard Wolff - @ewolff