-
This definition suggests categorizing messages between `events` and `actions`.
I think the distiction is very natural but the industry is leaning towards `events` vs `commands`. These names come fr…
-
This more fundamental question as soon as the whole idea of centralized event store is somehow against the distributed design :-)))
Have you ever considered more design where each events are only s…
-
`main()` should never contain anything generated by the design. By generating content in `main()` it means after I customize my `main()` (always, e.g. to add TLS and CLI support), if my design changes…
-
## Preamble
Idea:
Title: General architecture & patterns for status react
Status: Draft
Created: 2017/11/22
## Summary
Define and adhere to architecture vision for s…
-
In our microservices architecture REST API servers "only" for:
- Domain CRUD operations
- Bridge to push events to event bus for HTTP only clients
On the other hand, whole architecture follows sa…
-
snapshots In EventStore can be useful for performance.
Are you planning to support snapshots? If not, why?
-
Hi,
Great job with that project. I'd would like to add my feedback about the future of **domain events and integration between microservices**. I would like to suggest to apply event sourcing in the …
-
Part of the appeal of using EF as opposed to a micro-ORM like Dapper is the first-level caching (to my knowledge, Dapper doesn't do this).
However, by placing the DbContextScope (or any Unit of Wor…
-
I just started working on https://github.com/dotnet-architecture/eShopOnContainers/issues/305 and got an interesting situation... I can't normally describe the return type for OrderController.GetOrder…
-
I've been exploring an alternative to way that async actions are done in redux, and I'd appreciate any comments others might have on what I've done.
To illustrate my approach, I've changed the async …