Skip to content

CQRS pattern #2

@ghost

Description

Hi. Thank you for article and repository. Trying to learn some thing from it.
This is not an issue, just an question.
Have you seen similar implementation, but with Event Sourcing and CQRS patterns.
Like, when Tickets or Users API are just an gateway and moreover those are separated in Write and Read sides.
As well command handlers, event handlers, projections, notifiers, query handlers are incorporated just to provide full event-sourcing cycle of Ticket API as example + gRPC inter-service communication.
Or this is something too complicated and nobody is willing to spend time for open repository to showcase good practices?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions