Self-contained systems

from Wikipedia, the free encyclopedia

Self-contained system (SCS) is an architectural pattern of information technology , are separated in the functions in a plurality of independent systems. In this way, the overall logical system becomes a collaboration between several small software systems.

Features of self-contained system

SCS have the following properties:

  1. Each SCS is an independent web application.
  2. Each SCS is developed by a team.
  3. Communication with other SCSs or third-party systems should - if possible - take place asynchronously.
  4. An SCS can optionally have a service API.
  5. Every SCS must contain data and logic.
  6. An SCS should make its feature usable for end customers with a UI.
  7. To avoid tight ties, an SCS must not share a business code with other SCS.

Implementations implement such large systems - especially web applications.

Self-contained systems and microservices

Self-contained systems are similar to microservices , but there are some differences: A system contains fewer SCS than microservices. In addition, microservices can communicate with other microservices - even synchronously. SCS, on the other hand, should ideally not communicate at all or only communicate asynchronously. Finally, microservices can have a separate UI while an SCS contains a UI.

application

There are some systems that are based on SCS ideas - for example at Otto and GALERIA Kaufhof.

Web links

Description of the SCS approach on scs-architecture.org

Individual evidence

  1. ^ Self-contained Systems website .
  2. heise developer blog on self-contained systems .
  3. Original article on the ideas .
  4. Codecentric Blog .
  5. Self-contained Systems Website: SCS vs. Microservices .
  6. Otto Blog .
  7. Kaufhof blog .