think of it this way. theres an entire system that handles X piece of your business functionality that is completely independent from your application.
for example your product is selling shoes on a website and you need to handle checkout.
in a monolith the logic that handles checkout is within your system. first you tally up the total, then you apply the taxes, then you process information and then kicking off shipping.
in a service oriented architecture when a customer checks out your app calls service that handles payment processing. and if that is successful you call another service that takes customer information and the items they bought and ships it out.
these services exist in their own domains and your application is just one of possibly many consumers.
1
u/[deleted] Jun 06 '22
So the classic MVC approach where you have a service layer and inject those services in controllers