Lesson 153 - Service Based vs SOA

[@shitshow_1]

Amazing video, Mark, this is one of the concepts, something I couldn't understand even after reading loads of texts from blogs and articles.

[@markrichards5014]

Glad you liked it!

[@scottsnelson1]

From now I am going to link to this video whenever I need to explain this. Thanks for creating it!

[@markrichards5014]

That'a great! Thanks

[@alfredoquintanalopez2265]

It would be great to have a full video about Service-Oriented Architecture. Thanks!!!

[@markrichards5014]

Stay tuned! It's on its way

[@mahdi5796]

Very well explained. Thanks

[@ProteanCompany]

Suppose you have two services sharing the same database. One is about batch building, which involves the production of your batches, and the other is about the quality assurance of those batches. They are two different modules with their own workflows and activities, but it is obvious that since they are in the same database, a quality assurance table has a foreign key to the batch that is under inspection. Now, if you decide to separate the database, what happens to the foreign key in my quality assurance module to the batches table? Do I still keep the ID without hard checking? Do I need to change it to a link to the resource? Do I have to change it to a "universal code" of my batch?

[@giankarloslopezvasquez]

It's great!. I have a question, there is a section on the AWS page where it mentions how to move from a service-oriented architecture to a microservices architecture, and they give a comment like: "Microservices architecture is an evolution of the SOA architectural style", I thought. which was an evolution of the service-based architecture. This caused me confusion, well I'm going to read the recommended book anyway. Thanks anyway, seriously. Greetings from Peru!

[@markrichards5014]

Microservices evolved form needing more effective deployment pipelines as well as better domain partitioning (think DDD). So I guess in a way it evolved from SOA because SOA did neither of those well. Service-based architecture sort of evolved from Microservices as teams realized they didn't need such fine-grained services. I suppose its a chicken-and-egg scenario 🙂

[@sant4398]

For the SOA drawing, it would be great to add a client app to understand workflows. Unfortunately, it's not really clear what happens in the system when a company employee tries to use a system built OTO SOA.

[@markrichards5014]

The client app really is independent from the services, so it can vary greatly. It can be a desktop, web app, or even another system interface.

[@asugarapsa]

Too abstract, I don't follow.

[@morvanabonin]

He suggested reading the books if you wanna more details/to go deep about it.

[@vinicamposdev]

What part? If you want some more detailed information in one topic, ask in the comment. But this serie of video has a lot of other topics that you can verify. This is the 153, so there are a lot that are already told.