Scoping CQRS and Event-Sourcing Guidance Project

I am collaborating with the patterns & practices team. We are considering doing a guidance project on implementing systems using the Command & Query Responsibility Segregation (CQRS) approach. This is not going to be a framework or reusable components. We are positioning this project as a learning journey and envision providing an experience report that describes building a sample app (reference implementation) to showcase various CQRS and Event Sourcing (ES) concepts & techniques. We will include explanations of various trade-offs and architectural decisions made along the way. Of course, we will publish the reference implementation/sample app to complement the written guidance.

We are not into chasing elusive silver bullets. Our ultimate goal is produce practical guidance for real world development problems.

We are interested in your perspectives, your needs and your suggestions on what you’d like us to focus on.

Today we open the first round of public consultation with a questionnaire to help us direct our exploration. Depending on your feedback and related priorities we will produce an initial backlog which we will also invite the community to comment/vote on.

If you care about CQRS, ES, Domain-Driven Design and good design practices, please take part in this consultation process. Both real world experiences and the need to be successful with CQRS in the near future are valuable perspectives.

Comments (3)

  1. Here you have the URL where you can get the CQRS Guidance documentation and the sample CQRS application:  

  2. I would like to know the status of the guidance says:

    I would like to know the status of the practical guidance for real world development problems.

    Thaks you

  3. [Offtopic] DDD says:

    Hola, César. Estoy leyendo tu libro sobre Arquitectura en N-Capas y hay una errata que se repite continuamente: "así mismo" en lugar de "asimismo". Por lo demás el libro me está causando una buena impresión, aunque echo en falta que no se utilice NHibernate como ORM. Sinceramente, en la actualidad NHibernate es superior a Entity Framework y el desacoplamiento de las capas se logra de una forma más limpia y elegante. Con Entity Framework… se genera cierto código "spaguetti".

Skip to main content