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

When I use removeItem state operator then TypeScript complains that message object can be possibly undefined even though I specified the type for removeItem operator. I could fix the issue with optional chaining but that is not possible if I want to use a utility library like Ramda

![image](https://user-images.githubusercontent.com/14946081/104027016-135aed80-51c7-11eb-9316-9b3dbf5b79bf

Wish to request a new event source for HubSpot, to emit an event when a blog post is deleted. Also would be great to emit an event whenever a blog post is edited.

What is this bug about?

When we bootstrap the chat demo application by npx [email protected] init, the client uses old API routes, causing a 404 error.

What is the expected result?

When we bootstrap the chat demo application, it works as-is.

What is the actual result?

The chat demo application is not usable, since the client can't fetch from the back-end.

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

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