event-sourcing

https://github.com/kgrzybek/modular-monolith-with-ddd/blob/54d209639e501301e879aa0d0a84c9ea49e4689e/src/Modules/Meetings/Domain/Meetings/Rules/MeetingAttendeesLimitMustBeGreaterThanGuestsLimitRule.cs#L1-L21

I believe the comparison operator used in the IsBroken method is wrong because the rule is checking that meeting attendees limit must be greater than guests limit.

For an implementation of #126 (PostgreSQL driver with SKIP LOCKED), I create a SQL table for each consumer group containing the offsets ready to be consumed. The name for these tables is build by concatenating some prefix, the name of the topic and the name of the consumer group. In some of the test cases in the test suite, UUID are used for both, the topic and the consumer group. Each UUID has

We can get the response, but that API call only returns metadata, the /details endpoint that returns actual answer data is not available.

Ref: https://developer.surveymonkey.com/api/v3/#api-endpoints-get-surveys-survey_id-responses-response_id-details

In src/internal/state-context-factory.ts it is noted:

// In doing this refactoring I noticed that there is a 'bug' where the
// application state is returned instead of this state slice.
// This has worked this way since the beginning see:
// https://github.com/ngxs/store/blame/324c667b4b7debd8eb979006c67ca0ae347d88cd/src/state-factory.ts
// This needs to be fixed, but is a 'breaking' ch

I know it's not a course about RESTful principles but maybe you'll consider in the future extracting resource id from request body to path parameter ?

https://github.com/aspnetrun/run-aspnetcore-microservices/blob/c30712aa099bc335f5613a3b196ea1e943f800a5/src/Services/Catalog/Catalog.API/Controllers/CatalogController.cs#L85

Search before asking

• I had searched in the issues and found no similar issues.

Documentation Related

There is a missing file eventmesh-runtime/conf/rocketmq-client.properties which is required to deploy eventmesh-runtime in master branch

Are you willing to submit PR?

• Yes I am willing to submit a PR!

I would like to review the docs and explain also de concepts behind some decisions.
Things needed to explain:

• DDD objectives and reasons why.
• Core concepts like
  • bounded context
  • anti corruption layer
  • domain
  • value objects VS entities
  • aggregates
  • aggregate root
  • layered architecture and each one responsibility
  • reasons for the command and query bus
  • the even