Tag: cqrs


Found 130 results for 'cqrs'.


1) web-applications - How do you handle a web application POST request with event sourcing?
2) design - Command handling fail feedback with CQRS
3) domain-driven-design - CQRS, How to query aggregate root using others fields rather than GUID (ID)?
4) architecture - CQRS and Transactional Event Sourcing, problem while recreating Read DB
5) design-patterns - CQRS command that needs to work with multiple aggregate roots
6) domain-driven-design - What is the most appropriate way to launch an API gateway on a massive domain?
7) domain-driven-design - Can you rebuild/create new read models without Event Sourcing?
8) cqrs - CQRS-Event Sourcing: how to process events in the expected order inside the read model
9) domain-driven-design - designing events for an event sourcing based application
10) event-programming - How do I deal with side effects in Event Sourcing?
11) domain-driven-design - CQRS with an Event Log and without Event Sourcing
12) cqrs - Event Sourcing CQRS and request events ending at Requested
13) domain-driven-design - CQRS and DDD terminology
14) domain-driven-design - Event Sourcing and cross-context aggregate
15) domain-driven-design - Can command handlers be separated from aggregate roots in CQRS
16) domain-driven-design - Using Event Sourced Aggregate Roots with the Specification Pattern
17) cqrs - Event Sourcing - Multiple events or a single for a change on one aggregate?
18) domain-driven-design - How to implement a process manager in event sourcing
19) domain-driven-design - Event sourcing and sync between write and read model
20) domain-driven-design - Upholding business logic and invariants in an event sourced CQRS architecture
21) domain-driven-design - Handling aggregate root with deep object hierarchy
22) domain-driven-design - CQRS + Event Sourcing: (is it correct that) Commands are generally communicated point-to-point, while Domain Events are communicated through pub/sub?
23) domain-driven-design - DDD, Saga & Event-sourcing: Can a Compensate Action simply be a delete on the event store?
24) cqrs - How to update an event log in case of new events
25) design-patterns - Modify Command object inside decorator of CommandHandler(CQRS) or any other practice for avoiding duplication
26) domain-driven-design - Should CQRS Command perform a Query?
27) domain-driven-design - In an event sourced system, how do I get a current state of an entity?
28) domain-driven-design - How to model domain events so that the denormalizers can fill highly denormalized read models
29) domain-driven-design - Am I doing CQRS the correct way?
30) domain-driven-design - With event sourcing, how to get the response of a call that is a side-effect?
31) domain-driven-design - How exactly should a CQRS Command be validated and transformed to a domain object?
32) domain-driven-design - CQRS / DDD. Domain event and synchronisation with read model
33) validation - Where to put format validation in a CQRS “stylish” domain model?
34) sql-server - Can SQL Server and Mongo be used together?
35) architecture - Event Sourcing , sagas, bus and eventual consistency
36) domain-driven-design - In CQRS/ES should database calls be done in command handlers or domain models?
37) domain-driven-design - Does CQRS need to be fire and forget, If we need to read guarantee after command?
38) design - CQRS: Is it an antipattern if the Command invokes a database interface which contains business logic?
39) cqrs - CQRS - How can a command properly validate when queries are required?
40) architecture - Event Sourcing/CQRS for Self-Related Entities
41) versioning - Event sourcing, replaying and versioning
42) validation - Is it a bad practice or uncommon to save "Invalid operation attempted" events in an Event Store when doing Event Sourcing?
43) cqrs - Rewrite Events in EventStore
44) architecture - Designing a hierarchical structure with lots of reads and writes?
45) cqrs - CQRS, What reasons cause read model update delay? How to prevent user from taking inconsistence data?
46) cqrs - Circuit Breaker + Retry - Repository or Application Layer
47) domain-driven-design - One read model project/microservice for all other bounded contexts - is it a good idea?
48) web-services - REST Service and CQRS
49) architecture - Serverless event-sourced architecture using AWS offerings
50) cqrs - How to store Sagas with Event Sourcing