cqrs

Event Sourcing CQRS using Axon

Reading Time: 4 minutes Event Sourcing and CQRS are two of the original patterns for data management in a Microservices architecture. In this Blog, we understand the various data management patterns for microservices. What is Event Sourcing? At the high-level, Event Sourcing act like storing the state of the application in the form of domain events. I have also used a working example for Event Sourcing using Axon and Spring Continue Reading

Parameters Resolvers in Axon

Reading Time: 2 minutes Hi! In this blog, we will talk about the parameter resolvers in axon which help us build and model complex business entities required for the CQRS framework. Introduction What is Axon?It is a Java Framework, It allows to build of DDD (Domain Driven Design), CQRS (Command Query Responsibility Separation), and Event Sourcing as well.It helps in building several microservices from the system which would be easy to Continue Reading

two businessmen outdoor using technology

Introduction to CQRS(Working, Uses, Benefits)

Reading Time: 2 minutes Overview The Command and Query Responsibility Segregation (CQRS) pattern separates read and write operations for a data store. Reads and writes may take entirely different paths through the application and may be applied to different data stores. CQRS relies on asynchronous replication to progressively use writes to the read view so that changes to the application state instigated by the writer are eventually observed by the reader. How CQRS Works Consider, for Continue Reading

A Brief Introduction to Axon Framework

Reading Time: 3 minutes Need for Axon Framework Axon Framework is designed to support developers in applying the CQRS/DDD architectural pattern and Event Sourcing. It helps developers build easily scalable and maintainable applications by providing implementations of some basic building blocks, such as Aggregates, repositories, and event buses  Axon Framework, founded by Allard Buijze also working for Trifork, is an open source product with version 3 planned for Q1 2016. CQRS Example Using Continue Reading

Understanding Java enums

Introduction to CQRS and Event Sourcing

Reading Time: 3 minutes CQRS CQRS (Command Query REsponsibility Segregation) is a very simple pattern and not new at all. CQRS is based on the Command Query Separation (CQS) principle which was suggested by Bertrand Meyer. CQS suggest that we divide the operation on domain object into two distinct categories: Queries and Commands. The Command and Query Responsibility Segregation(CQRS) it’s an architectural Pattern Where the main focus is to Continue Reading

Read Model and Write Model | CQRS | Reactive Architecture

Reading Time: 2 minutes Read Model and Write model…what they are and from where they have been driven. In this blog we’ll discuss about CQRS, read model and write model in brief. CQRS – What, Why and How … ? Till the time we have used a number of different architectures, patterns and implementations that revolve around the core concept of Command Query separation (CQS). The core ideas behind Continue Reading

Lagom Zero Hour: CQRS Concepts

Reading Time: 4 minutes In this blog, we will discuss CQRS and how it is different from old approaches. CQRS stands for Command Query Responsibility Segregation. The approach that individuals use for interacting with a data system is to treat it as a CRUD datastore. By this, I mean that we have a mental model of some record structure. We think about producing new records, scanning records, updating existing records, Continue Reading

Concepts of CQRS

Reading Time: 3 minutes In the previous blog, we have learnt what Event Sourcing is. Moving forward, we will dive into the concepts of CQRS, understanding its meaning, why is it required and its advantages. CQRS Pattern CQRS stands for Command Query Responsibility Segregation. As the name suggests, we split the application in two parts: Command-Side and Query-Side. Now one will ask what this command and query means? Okay, Continue Reading

Introduction to Event Sourcing

Reading Time: 3 minutes Have you ever come across the terms Event Sourcing and CQRS? This blog is a good start to gain basic knowledge about the two. Here, we will learn what is Event Sourcing? And what are the benefits of having an event sourced application? CQRS will be covered in the next blog. What is Event Sourcing? Event sourcing is the practice of capturing all changes as Continue Reading

DATA PERSISTENCE IN LAGOM

Reading Time: 5 minutes Are you finding it difficult to understand lagom persistence? Don’t worry because help is right here. In this blog, we will learn about lagom persistence with the help of a simple application and also discuss its theoretical aspects. Before we begin, make sure you know about Event Sourcing and CQRS. You can read about it in details from this link . Choosing a database When Continue Reading

Integrating Play app with Lagom application

Reading Time: 2 minutes What is Lagom? Simply put, it is a microservices tool. Lagom is a microservices framework that guides developers in moving from monolithic to a scalable, resilient microservice based systems. It is a platform delivering you not only the microservice framework but also a whole tool set for developing applications along with creating, managing and monitoring your services. According to Lightbend the focus should not be Continue Reading

Lagom Framework: The Legacy WordCount Example

Reading Time: 3 minutes What is Lagom? Lagom is an open source micro-service framework, built with Akka message-driven runtime and Play web framework and finally light bend service orchestration. Mixing all these technologies abstracts away the complexities of building, running, and managing microservice architectures. Lagom is a Swedish word meaning “just the right amount”. Often, when people talk about microservices, they focus on the micro part of the name, Continue Reading

CQRS in a jiffy!

Reading Time: < 1 minute Segregate operations that read data from operations that update data by using separate interfaces. This pattern can maximize performance, scalability, and security; support evolution of the system over time through higher flexibility; and prevent update commands from causing merge conflicts at the domain level. The term sounds heavy, but the concept is not. At least, this is what we discovered at the end of our regular Continue Reading