Software:Self-contained system
In computing, self-contained system (SCS) is a software architecture approach that focuses on a separation of the functionality into many independent systems, making the complete logical system a collaboration of many smaller software systems.[1]
Self-contained system characteristics
SCSs have certain characteristics:
- Each SCS is an autonomous web application.
- Each SCS is owned by one team.
- Communication with other SCSs or third-party systems is asynchronous wherever possible.
- An SCS can have an optional service API.
- Each SCS must include data and logic.
- An SCS should make its features usable to end-users by its own UI.
- To avoid tight coupling an SCS should share no business code with other SCSs.
- Shared infrastructure should be reduced to increase availability and decrease coupling.
Implementations[2] create larger systems using this approach – in particular web applications. There are many case studies[3] and further links available.[4]
Self-contained systems and microservices
While self-contained systems are similar to microservices there are differences: A system will usually contain fewer SCS than microservices. Also microservices can communicate with other microservices – even synchronously. SCS prefer no communication or asynchronous communication. Microservices might also have a separate UI unlike the SCS that include a UI.[5]
Usage
There are quite a few known usages of SCS – e.g. at Otto,[6] Galeria Kaufhof,[7] and Kühne+Nagel.[8]
References
- ↑ "Self-contained Systems Website". http://scs-architecture.org/.
- ↑ "Codecentric Blog". 12 January 2015. https://blog.codecentric.de/en/2015/01/self-contained-systems-roca-complete-example-using-spring-boot-thymeleaf-bootstrap/.
- ↑ "Case Studies on the SCS website" (in en). https://scs-architecture.org/case-studies.html.
- ↑ "Links on the SCS website". http://scs-architecture.org/links.html.
- ↑ "Self-contained Systems Website: SCS vs. Microservices". http://scs-architecture.org/vs-ms.html.
- ↑ "Architecture principles (used to develop the Otto shop)". https://www.otto.de/jobs/en/technology/techblog/blogpost/architecture-principles-2013-04-15.php.
- ↑ "Kaufhof Blog". https://galeria-kaufhof.github.io/general/2015/12/15/architektur-und-organisation-im-galeria-de-produktmanagement.
- ↑ "From Monolith to Microservices". https://kuehne-nagel.github.io/monolith-to-microservices/.