Lesson126 - Is SOA Dead?

[@simonk1844]

Thanks! This is the best definition of SOA I've seen anywhere, including coverage of its core pros and cons.

[@markrichards5014]

Thanks Simon!

[@softwarearchitecturematter4482]

Nice video. In my opinion, SOA was victim of its hype and success. SOA became synonym with Web Services . Everyone started using Web Services and distributed architecture regardless of business case. SOAP was bulky and hence the performance issues.

[@markrichards5014]

Agreed! I like that - a victim of its own success and hype - sort of like microservices??? :-)

[@softwarearchitecturematter4482]

@@markrichards5014 :). Hi Mark, you should post more videos like this where you are giving your personal opinions, analysis and real life case studies.

[@markrichards5014]

@@softwarearchitecturematter4482 Good idea - I will do more of these type of lessons this year!

[@pranavtanpure8131]

Hello Sir, Thank you so much for providing such an amazing playlist..... Can please make playlist on XML schema, XML, how SOAP working internally in depth. Looking forward for your response. Regards.

[@carlosjavierbellotti6660]

Great explanation as ever Mark. I justify the use of SOA in environment in which the organization is too old and have too many heterogeneous systems with heterogeneous communication protocols that needs to interact. Out from this, it's best to keep far from SOA :D. Regards

[@markrichards5014]

Well said - I couldn't agree more!

[@stouneua]

These ESB's evolved and rebranded into integration platforms, like Dell Boomi or Mulesoft

[@markrichards5014]

Yes, and that is a very good thing because we still sometimes need to abstract the integration of other systems. You can still have an event bus and not be immersed in the SOA world. ESB != SOA

[@ashishjain601]

I am working in soa architecture in one of the biggest investment bank since 2015. I am proposing the client since long to migrate to microservice but bank don't want more investment.

[@sant4398]

While reading your book, probably, I found this architecture style most confusing me and I would be happy and very appreciate to get answers of few different attitude questions: 1. On the chart which describes the general view of the architecture shouldn't the Application services and infrastructure services be available to the business services directly but not through the enterprise services? It looks like a business service can't communicate directly with the enterprise services, but following your explanation it sounds for me like it should. 2. I read corresponding article about this architecture style on the Wikipedia, and it has some major difference regarding some characteristics with what read in your books. First of all, it's coupling. While in your book it says SOA brings high level of the coupling in the system, the Wiki article says it provides high level of decoupling. 3. At the end, Wiki says that SOA can be implemented by using microservices or web services. And this confuse me, as microservices architecture is considered nowadays as one of the most modern architecture styles. 4. At some point, SOA for me looks like has some characteristics of Microkernel architecture style, as we can consider the orchestration or chorographical services as core of the SOA, which functionality extended with set of service providers. ))) Please, correct me if I get it wrong. Because at some point I can interpret SOA as Microkernel build OTO microservices. :) Thanks.

[@markrichards5014]

Hi SanT. I'll answer some of your questions. Regarding 1, Usually application services are scoped to only a particular application and therefore have an attached user interface. Business services generally span multiple application contexts, so while you can, it generally not done. Regarding 2, the coupling comes into the tight contracts that exist between services, and also the high SEMANTIC coupling between service types to complete a single business request. Regarding 3, no, no, no, SOA is NOT microservices! I wrote a book on this (O'Reilly, Microservices vs. SOA). Regarding 4, Look at lesson 160 in a couple of weeks to see the differences between Microkernel and SOA.

[@yanjustino6491]

Nice videos, Mark. But I disagree with the reduction of SOA to architecture style. There are a huge literature illustrate SOA as service oriented paradigm instead just architecture.

[@markrichards5014]

Point well taken. AND, I suspect Microservices will fall into that same sort of paradigm...

[@ksurendar2647]

As per me, Its not dead. I'm continuing my development of ESB services from past 8 years in organizations projects.

[@ashishjain601]

It's old applications which client don't want to migrate.

[@stomic50]

Hey Mark, quick question: would SOA architecture be a perfect candidate in your opinion for cloud native transformation?

[@markrichards5014]

You know of course I must answer that with the traditional "it depends" :-). However, no, I would say no, SOA is not the perfect candidate for cloud transformation. Microservices is a much better fit, as is event-driven and space-based architecture.

[@stomic50]

@@markrichards5014 But microservices are the core part of cloud native transformation, aren't they?

[@markrichards5014]

@@stomic50 Indeed they are! But Microservices is entirely different from SOA. See the link in the description for the book I wrote "Microservices vs. SOA" - it is a free PDF

[@maielshiashi1944]

Did I get the wrong book or something? the ratings of the architecture in the video is different from the ratings in the book.

[@markrichards5014]

No, I just chose to add a few more characteristics to the short video from our book. The characteristics I mentioned in the video were an extension to the ones published in our book. Sorry for the confusion!

[@maielshiashi1944]

@@markrichards5014 Yeah I noticed that there're new characteristics introduced in the video. What I meant is that for example, the testability characteristic of Service-Based Architecture in the book is given 4 stars. On the other hand, in the video 7:31, the testability is given only one star.

[@markrichards5014]

Ah, now I see the problem - service-based architecture is not the same as service-oriented architecture. These are two entirely different architecture styles. In the video I was referring to service-ORIENTED architecture, but I think you were looking at the ratings for service-BASED architecture. Very confusing I know!

[@maielshiashi1944]

​@@markrichards5014 Yeah it's confusing. Thank you for pointing that out!

[@42svb58]

This sounds like ERP systems especially SAP

[@ashishjain601]

It's not dead but It's become old woman who is no more attractive. Microservices and event driven is new girls in the town.