Skip to content

Architecture styles

Where the boundaries go and what each costs transfers to every stack. The recurring mistake is treating microservices as a default rather than a trade against organisational size.

Layer 17 entities0 started
  • modular-monolith

    Not started. Becomes a package with its own syllabus once it begins.

    candidate
  • microservices

    Not started. Becomes a package with its own syllabus once it begins.

    candidate
  • event-driven-architecture

    Not started. Becomes a package with its own syllabus once it begins.

    candidate
  • cqrs

    Not started. Becomes a package with its own syllabus once it begins.

    candidate
  • event-sourcing

    Not started. Becomes a package with its own syllabus once it begins.

    candidate
  • ddd

    Not started. Becomes a package with its own syllabus once it begins.

    candidate
  • hexagonal-architecture

    Not started. Becomes a package with its own syllabus once it begins.

    candidate