How do I handle schema evolution in event sourcing?

The project points to resources like the Stamina library for versioning and auto-migration at read time, and academic papers on data conversion, offering practical strategies for managing long-term data viability.

What are the best practices for testing CQRS systems?

It includes articles on property-based testing with functional programming and testing persistent actors in Akka, providing insights into validating event-sourced domains through algebraic laws and unit tests.

Event Sourcing with Akka vs using a traditional database, which is better for scalability?

Resources discuss CAP trade-offs; for example, Akka Persistence is more consistent, while Eventuate offers higher availability, helping you choose based on your system's scalability and consistency needs.

How to implement versioning in Event Sourcing with Akka?

Refer to linked talks by Greg Young and the Stamina library, which provide tools and concepts for versioning persisted data and auto-migrating older versions to be compatible with current event classes.

Where can I find Scala examples for Domain-Driven Design?

The repository includes articles on hexagonal architecture and free monads, as well as frameworks like Fun.CQRS, offering code illustrations and functional domain modeling approaches in Scala.

What are the trade-offs of using Event Sourcing in production?

Expert talks cover issues like versioning, CAP theorem implications, and data conversion challenges, providing balanced perspectives on complexity versus benefits in distributed systems.

Advanced Topics in Event Sourcing / CQRS / DDD

A curated collection of advanced resources on Event Sourcing, CQRS, and DDD with a focus on Scala and Akka implementations.

GitHub

What is Advanced Topics in Event Sourcing / CQRS / DDD?

Advanced Topics in Event Sourcing / CQRS / DDD is a curated knowledge repository focused on advanced architectural patterns for building scalable, maintainable systems. It compiles expert talks, open-source tools, articles, and academic papers to help developers deepen their understanding of Event Sourcing, CQRS, and DDD, particularly in Scala and Akka ecosystems.

Target Audience

Software architects and senior developers building or maintaining distributed systems who want to implement or refine Event Sourcing, CQRS, or DDD patterns, especially those using Scala and Akka.

Value Proposition

It saves time by aggregating high-quality, vetted resources from industry experts, providing practical insights into implementation challenges like versioning, consistency, and testing that are often glossed over in introductory materials.

Overview

Advanced Topics in Event Sourcing / CQRS / DDD. PRs welcome. This "project" follows Scala's CoC.

Use Cases

Best For

Learning advanced Event Sourcing and CQRS concepts beyond basics

Related Projects

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub

110 stars4 forks0 contributors

Understanding versioning and schema evolution in event-sourced systems

Exploring Scala and Akka implementations of these patterns

Researching CAP theorem trade-offs in distributed Event Sourcing

Finding functional programming approaches to domain modeling

Studying real-world open-source frameworks like Stamina or Fun.CQRS

Not Ideal For

Teams seeking ready-to-use code templates or boilerplate for rapid prototyping
Developers working with non-JVM ecosystems like .NET or Node.js who need language-specific guidance
Beginners looking for introductory, step-by-step tutorials on basic Event Sourcing concepts

Pros & Cons

Pros

Curated Expert Insights

Aggregates high-quality talks from experts like Jonas Boner and Greg Young, providing distilled wisdom on advanced topics such as versioning and CAP trade-offs, as highlighted in the README's starred entries.

Scala/Akka Ecosystem Focus

Emphasizes practical implementations using Akka Persistence and related tools, with specific resources on frameworks like Stamina for schema evolution and Fun.CQRS for pluggable backends.

Practical Challenge Coverage

Includes discussions on real-world issues like data conversion, testing, and consistency, drawing from academic papers and articles that address nuances often missed in introductory materials.

Functional Programming Integration

Highlights the relationship between Event Sourcing and functional programming, with talks on type-safety and algebraic laws, aiding in domain modeling with statically typed approaches.

Cons

Technology Stack Limitation

Heavily centered on Scala and Akka, making it less relevant for developers using other technologies or languages, as the README admits a preference for type-safe, functional approaches in this ecosystem.

Absence of Hands-On Code

As a resource collection, it lacks executable examples or tutorials, requiring users to seek additional sources for practical implementation, which the README doesn't provide beyond links.

Potential Resource Obsolescence

Some linked talks and articles date back to 2015-2017, which may not cover the latest advancements in fast-evolving fields like distributed systems, despite being curated.

Static Repository Nature

Does not offer interactive elements like forums or Q&A, limiting support for troubleshooting or community discussion, as it's primarily a passive knowledge base.

Frequently Asked Questions

Home

Domain-Driven Design

Awesome Event Storming

Awesome EventStorming

Stars2,385

Forks188

Last commit1 year ago

Context mapping

Context Mapping is a technique from Domain-Driven Design (DDD) that helps visualize the relationships between bounded contexts and the teams that own them. It provides a structured way to analyze existing systems or plan new architectures by mapping out dependencies, governance, and model propagation. This repository offers practical resources to make context mapping more accessible, including a cheat sheet and a starter kit for collaborative tools like Miro. ## Key Features - **Nine Context Map Patterns** — Includes Open-host Service, Conformist, Anticorruption Layer, Shared Kernel, Partnership, Customer/Supplier Development, Published Language, Separate Ways, and Big Ball of Mud to describe various integration and governance scenarios. - **Three Team Relationships** — Defines Mutually Dependent, Upstream/Downstream, and Free relationships to clarify organizational and technical dependencies. - **Practical Starter Kit** — Provides a pre-built Miro board with all pattern objects and examples to kickstart remote collaboration sessions. - **Context Map Cheat Sheet** — A quick-reference guide summarizing all patterns and relationships for easy consultation during design workshops. - **Best Practices Guidance** — Recommends using small, focused context maps for specific questions rather than creating overwhelming monolithic diagrams. ## Philosophy Context Mapping aims to make complex sociotechnical architectures understandable by providing a shared visual language that bridges technical models and team dynamics, emphasizing clarity and targeted communication over completeness.

Stars1,805

Forks154

Last commit11 months ago