Skip to content

Plans for the project #3

Description

@aschrijver

Came here via the videos which I absolutely loved! I am a Go noob, who's looking into building a fediverse app based on GoFed activity library. Prior to that I'd been looking to do that in a NestJS DDD/CQRS-style architecture, using nestjs-cqrs module.

In the video you mention further work on the app, maybe as reference impl and production-ready OAuth2, but I notice that most commits date from the time of the videos. Do you have further plans with this?


Some things I'd like to mention:

  • I'd add some topics to the repo, like 'cqrs', 'ddd', 'event-sourcing', 'eventstore', etc. for findability, as well as a mention of "DDD" and "CQRS" in the project description.
  • These great videos should not be missed. I'd add their links to the README.

Regarding the code:

  • Seemed to me the process manager concept touched really close to that of Sagas in DDD-terminology.
  • The project is a great candidate for breaking out the DDD/CQRS concepts to their own library (like NestJS did) and save other some of that "boring work" you talked about.
  • Project could benefit from an intuitive 'clean architecture' folder structure, especially for larger DDD apps.
  • With your BDD setup you come real close to Cucumber-style testing where your Gherkin feature description is text-only, and read by the code.

Edit: There is a cucumber impl in Go actually I now see: godog

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