Skip to content
This repository was archived by the owner on May 14, 2022. It is now read-only.

Project structure for backend "CQRS" services #11

@ghost

Description

Given that project covers multiple business domains (Shipping, Warehousing, User, Authentication, Accounting, etc) and each of domains consists of multiple services:

  • Shipping
    -- REST/gRPC API GW
    -- WebSocket GW
    -- Command Service
    -- Event Handler Sevice
    -- Denormaliser Service
    -- Query Service

I need to think how to structure those services. Main target is to achieve service isolation so that single team/person could work on it without navigating over whole repository and it should be deployable as single unit. At the same time code sharing and package reuse should be heavy accepted. All those services should be scoped to its domain/sub-domain.

Metadata

Metadata

Assignees

No one assigned

    Labels

    researchThis issue requires research

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions