Skip to content

"SCS vs. Microservices" should not mix microservices with SCSs #17

@magro

Description

@magro

The page SCS vs. Microservices says "Of course it is possible to split an SCS even further so it consists of microservices". Because it's often said that microservices have their own database in order to be decoupled from other services (see e.g. Pattern: Microservices Architecture) I'd try to avoid the usage of the term "microservices" and rather prefer "subsystems" or "processes". This is just to start the discussion about terminology, which was also already questioned on the discussions page.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions