⚠️ IMPORTANT NEWS! 📰

I’ve been dealing with CQRS, event-sourcing and DDD long enough now that I don’t need working with it anymore unfortunately, so at least for now this my formal farewell!

I want to thank everyone who has contributed in one way or another. Especially...

• Jan, who introduced me to this topic.
• Dimitar, one of the last bigger contributors and maintainer.
• My last employer, who gave me the possibility to use all these CQRS modules in a big Cloud-System.
• My family and friends, who very often came up short.

Finally, I would like to thank Golo Roden, who was there very early at the beginning of my CQRS/ES/DDD journey and is now here again to take over these modules.

Golo Roden is the founder, CTO and managing director of the native web, a company specializing in native web technologies. Among other things, he also teaches CQRS/ES/DDD etc. and based on his vast knowledge, he brought wolkenkit to life. wolkenkit is a CQRS and event-sourcing framework based on Node.js. It empowers you to build and run scalable distributed web and cloud services that process and store streams of domain events.

With this step, I can focus more on i18next, locize and localistars. I'm happy about that. 😊

So, there is no end, but the start of a new phase for my CQRS modules. 😉

I wish you all good luck on your journey.

Who knows, maybe we'll meet again in a github issue or PR at i18next 😉

Adriano Raiano

Introduction

This is a sample implementation of CQRS / Eventsourcing Infrastructure in node.js using:

• domain
• eventdenormalizing
• viewmodel, read/write repository
• eventstore
• business-rules and validation

get it up and running

0. install and start Redis

1. start server in host and domain folder

   node server.js
   

2. direct your browser to

   http://localhost:3000
   

the source code is well documented to understand the core principles.

why should i care?

• Clarified CQRS - Udi Dahan
• Top 10 Reasons to do CQRS - Rinat Abdullin
• CQRS why, what, how - Jeppe Cramon

got the sample - where to go now?

This modules are the result of open sourcing parts of a large reallife project of a distributed system based on the principle of DDDD and CQRS. It's gone through a lot of iterations and should address most pitfalls.

The API is designed well so you can focus on the domain without worring to much about the infrastructure.

• domain

• eventdenormalizing

• viewmodel, read/write repository

• eventstore

• proper dequeing

• business-rules and validation

• message bus

• without distributing

Documentation can be found here

other examples

• https://github.com/smariussorin/EventSourcedMicroservices