Knoldus Blogs

Lagom Zero Hour: CQRS Concepts

March 6, 2019March 31, 2019Lagomcqrs, ES, lagom

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

June 19, 2018August 9, 2018Architecture, Database, event, Microservices, Tutorialcqrs, Database, Design, event sourcing, events, Introduction, learning, Microservice architecture design, technology

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

June 13, 2018August 9, 2018Architecture, Database, Microservices, Tutorialcqrs, Database, event sourcing, Introduction, learning, snapshots, technology

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

November 15, 2017August 9, 2018Cassandra, Database, Microservices, NoSql, ScalaCassandra, cqrs, data persistence, Database, event sourcing, lagom, lagom persistence, persistent entity, scala

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

March 31, 2017August 16, 2018Cassandra, Scalacqrs, kafka, lagom, Microservice architecture design, Microservices, Play Application, Play framework, Scalability

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

March 27, 2017March 27, 2017Big Data and Fast Data, Microservices, Scalacqrs, event sourcing, lagom, Lagom Architecture, wordcount

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!

January 31, 2016January 31, 2016Scalaakka persistence, cqrs, event sourcing

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