Are Microservices SOA Done Right?

Transcription

1 Are Microservices SOA Done Right? Jason Bloomberg 1

2 About Jason Bloomberg President of industry analyst firm Intellyx Agile digital transformation thought leader Write for Forbes, several blogs, biweekly newsletter the Cortex Buy my latest book, The Agile Architecture Revolution 2

3 Photo Credit: Alpha du centaure It s About Architecture! 3 The real question: is microservices architecture SOA done right? What is microservices architecture? What is SOA done wrong anyway? No argument of architects, please!

4 Photo Credit: Phil Manker Was First-Generation SOA SOA Done Wrong? First-generation SOA ESB-Centric Most or all services were Web Services XML was primary message format Yes, many times it was done wrong Didn t meet business needs Insufficient business agility Sometimes people actually got it to work! 4

5 Photo Credit: Cory Doctorow What About 2 nd Generation, REST-Based SOA? REST cleaned up a lot of the Web Services mess Abstracted, governed service interfaces still a challenge REST s architectural subtleties ambiguous & difficult REST-Based SOA still largely predated microservices 5

6 Web Services are contracted interfaces WSDL + other policy documents form the contract (all XML) Abstract underlying software RESTful services are also contracted interfaces Known by their URI & uniform interface Microservices are units of execution Container-centric (although containers not required) SOA Services vs. Microservices 6

7 Photo Credit: Neil Turner No More Lipstick SOA Services suffer from lipstick on the pig problem Complicated, problematic software exposed as services still complicated & problematic Call for best practices underlying service interfaces Highly modular, shared nothing code Independently deployable Easy to distribute & scale 7

8 Photo Credit: James Lee What are Microservices? Parsimonious, cohesive units of execution Designed to do one thing very well Contain everything from the operating system, platform, framework, runtime and dependencies, packaged as one unit of execution 8

9 Photo Credit: AJC Parsimony As small as they should be but no smaller As part of refactoring, ask: Would this microservice work better if it were smaller? Would this microservice work better if it were split into two or more microservices? 9

10 Cohesion Microservices should do one thing well Principle of modular programming since the 1960s Web Services often suffered from low cohesion 10

11 Cracking Open a Microservice Service Interface μservice Code Runtime Cache Shared nothing in the sense that each microservice has these elements Each element is itself parsimonious & coherent OS Elements 11

12 Photo Credit: Ananth BS Right Tool for the Job SOA Services become enterprise services Abstract & expose legacy functionality Leverage value of existing middleware Microservices better for greenfield development Cloud and container friendly Straightforward continuous delivery Also DevOps friendly 12

13 Microservices & Containers Containers support lightweight, rapid scalability & elasticity Microservices well-suited for containers Challenges: Managing state Keeping track of everything Integration, especially in dynamic environments 13

14 Photo Credit: Jitze Couperus What about Container- Oriented Architecture? Still in its formative stages Even so, doesn t look much like SOA, done right or not Not clear whether microservices-oriented architecture and containeroriented architecture will be or should be the same thing 14

15 Photo Credit: Lauren Coolman Container-Oriented Architecture & the Cloud Container-oriented architecture builds upon cloud architecture best practices Horizontal scalability Elasticity Automated recovery from failure Tunable data consistency 15

16 Photo Credit: Robert Couse-Baker The Answer? Microservices architecture is SOA + cloud architecture done right Not a fixed goal More of a journey of architectural discovery Not wrong vs. right, but getting better as we go 16

17 Thank You! Jason Bloomberg President, Send NOW to to download this presentation