SCSs and Microservices

SCSs stand out from deployment monoliths in the same way as microservices. A deployment monolith would implement the entire application in a single deployable artifact while SCSs divide the system into several independent web applications.

Because an SCS is a separate web application, it can be deployed independently of the other SCSs. SCSs are also modules of an overall system. Therefore, SCSs are independently deployable modules and consequently correspond to the definition of microservices.

One SCS can be split into several microservices #

However, an SCS may be split into several microservices. If the payment in the check out SCS of an e-commerce system causes a particularly high load, then it can be implemented as a separate microservice which can be scaled separately from the rest of the check out SCS. So, the check out SCS consists of a microservice for payment and contains the rest of the functionality in another microservice.

Another reason for separating a microservice from an SCS is the security advantage offered by greater isolation. Additionally, domain services that calculate the price of a product or quotation for all SCSs can be a useful shared microservice. The microservice should be assigned to a team like an SCS in order to avoid too much coordination.