4 ms·
How are microservices really different from SOA?
by ilaksh 13y ago
How are microservices really different from SOA?
- stock_toaster 13y agoIt does seem just like SOA to me, but maybe it implies even smaller services (that would seem to also imply more overhead due to extra requests, but maybe not)?
- Spearchucker 13y agoYou're right. Or maybe saying "I agree with you" is more pragmatic. Recent case in point - I have an app that fetches and saves a lot of data from and to a server. It has pretty heavy security requirements so I split out user registration and login into a separate server app. The client calls it, gets a token and uses it to access data in another service. A customer just asked to two-factor authN. I can make that change without affecting any of the business services. Getting it wrong means little more than a short-lived denial of service. In traditional SOA authN would be wrapped up with authR in a service interface or façade, fronting the monolithic app. Not nearly as extensible or flexible.
- twic 13y agoSOA is a lame enterprise approach, whereas microservices are a cool hacker approach. If someone knows a non-flippant difference between SOA and microservices, i'd be interested to hear it.
- aet 13y agoI think you nailed it
- stock_toaster 13y agoSome people like to give every nuance a new name. This seems especially prevalent in software development. I mean how else you going to get people to buy new books and read your blog posts?!
- dragonwriter 13y agoMicroservice architecture, as described, appears to be a SOA principles applied in a particular way (typically, to smaller units of functionality than are often considered with SOA), and with less baggage from association with WS-* standards (which, really, logically, aren't at all necessary to SOA, but have in many circles become so associated with it that its hard to say "SOA" without people thinking you mean "WS-*".)
- spitfire 13y agoSOA architectures are supposed to have formalized generic interfaces to services. EG: a standardized interface to a mailer, so you can pull out a mailer and replace it with another at will. In practice, most "SOA" architectures are microservices.
- bitcrusher 13y agoGenerally speaking, it's the lack of a linear service bus and orchestration. In a 'traditional' SOA architecture, the workflow is defined as a linear progression from one state to another, where each 'service' mutates ( or not ) the state of the data. Determining 'which' services are used/called in the service bus is typically defined in an orchestration. They definitely have some similarities, however one thing to note about 'Architecture' is that it's often more about ways of thinking about a problem as much as it is about 'solving a specific problem'. Another helpful comparison might be: SOA is like GNU Hurd and Micro-Services are like Unix.