BT

Facilitating the spread of knowledge and innovation in professional software development

Contribute

Topics

Choose your language

InfoQ Homepage CQRS Content on InfoQ

  • Advantages of CQRS

    Today’s applications are commonly unnecessarily complex or slow because of not using Command Query Responsibility Segregation (CQRS), Gabriel Schenker claims while stating he believes CQRS to be one of the most useful architectural patterns when used in the context of complex Line of Business (LOB) applications.

  • CQRS as a Style of Thinking

    A common context for Command-Query Responsibility Segregation (CQRS) is a collaborative domain with multiple users working on the same set of data, it is less suitable in domains with only a single user working on a piece of data, Udi Dahan explained when discussing CQRS in an interview.

  • The Basics of Event Sourcing and Some CQRS

    State transitions are an important part of our problem space and should be modelled within our domain, Greg Young states in a recent presentation focusing on basic event sourcing and how CQRS fits in.

  • Experiences Building a Reactive Event-Driven CQRS Application

    CQRS and Event Sourcing provide a clear and concise way to build distributed applications that adhere to the reactive manifesto, Duncan DeVore claimed in a recent presentation sharing his experiences building a distributed application using Akka and Scala.

  • Building a Reactive DDD and CQRS Based Application Using Akka

    DDD and CQRS are great for building scalable software considering concepts like bounded contexts, transaction boundaries and event based communication and is together with Akka a complete platform for building enterprise applications, Pawel Kaczor starts a three-part series building an reactive application based on these concepts.

  • DDD and CQRS Using the Functional Language F#

    A focus on behaviour and a more declarative style of code are two benefits for Domain-Driven Design (DDD) when moving from an object-oriented language like C# to a functional one like F#, Lev Gorodinski claims in a recent presentation, using an example that includes event sourcing and Command-Query Responsibility Separation (CQRS) to show some of the benefits and challenges in a move to F#.

  • CQRS Framework Axon 2.1 with Increased Event Handler Support and Performance Improvements

    Version 2.1 of CQRS framework Axon supports annotations and ordering of event handlers, a new conflict resolution together with performance improvements. The recently released version also adds compatibility with OSGi.

  • New C# based CQRS Tutorial available

    A new CQRS, Command Query Responsibility Separation, C# based Starter Kit to help developers get up and running with CQRS on .NET has been developed, not as a framework, but as a tutorial for developers interested in learning about CQRS, and as a possible starting ground for a CQRS based system.

  • CQRS Framework Axon 2 Features MongoDB Support and Performance Improvements

    The latest version of CQRS framework Axon supports MongoEventStore, which uses MongoDB as a backing store, and comes with a simplified API and performance improvements. The recently released version 2.0 also lets event objects be based on POJOs and annotations to define messages, payload and metadata.

  • CQRS Guidance Project On MSDN

    The Patterns and Practices team at MSDN recently announced a CQRS Journey Guidance project – the project walks through building a fictional Contoso Conference Management System using DDD, CQRS and Event Sourcing.

  • CQRS With Windows Azure

    CQRS is gaining popularity as a pattern suited for applications with high scalability and performance needs. In his article “CQRS On Windows Azure”, Mark Seemann uses an example to explore how to use this pattern with Windows Azure as the platform.

  • Axon Framework 1.0 Released

    The Axon framework from JTeam - an implementation of the CQRS and EDA patterns - has been released.

BT