How reimagined/resolve works
Main Components
• Client Layer – which primarily uses React (and optionally Redux) to interact with the back-end. This is where UI components, containers, and client-specific logic reside.
• Command & Query Handling – the server side distinguishes between the Command part (handling writes, invoking aggregates and sagas) and the Query part (handling read models).
• Domain/Business Logic – represented by aggregates (DDD) and sagas for side-effects and process management. The core business rules are implemented here.
• Event Sourcing Infrastructure – central to the framework, this includes event stores (and its various adapters such as eventstore-base, eventstore-lite, as well as adapters for MySQL, PostgreSQL, etc.), which store events as the source of truth.
• Read Model Builders – components that project events into queryable read models; these may have corresponding resolvers, projections, and connectors.
• Runtime Adapters and Modules – these are contained in the “packages/runtime” and “packages/modules” directories. They include adapters for external services (monitoring adapters, readmodel adapters, replicators, etc.), application scaffolding (create-resolve-app), and configurable pieces that integrate with different ecosystems.
• Tools and Scripts – available in “packages/tools” and “internal” directories, which help with building, testing, managing configurations, and working in a monorepo environment.
Out the Relationships and Data Flow
• Within the server, clearly separate and show:
– A Command Side: routes incoming commands to aggregates and triggers sagas.
– An Event Store: acts as the event-sourced backbone where events are recorded.
– A Query Side: shows how events are processed into read models, which are then served back to the client.
• Where integrations occur – such as authentication, authorization, and module extensions for additional functionality (e.g., modules for comments, administration, replication, uploading).
Architectural Patterns and Design Principles
• Event Sourcing – Use a central component to illustrate how events are stored and replayed to build state, instead of directly storing state changes.
• Modular and Extensible Design – Emphasize that the “modules” and “runtime adapters” sections allow replacing or enhancing parts of the system.
• Functional and Declarative Programming Model – While not depicted by specific symbols, note that the implementation style is functional (pure functions, immutability) throughout the architecture.
Relevant Technologies, Frameworks, and Libraries
• Mention React and Redux on the front end.
• Node.js as the runtime environment.
• Use of TypeScript (in many examples and templates) alongside plain JavaScript.
• Build and configuration tools (webpack, Babel, ESLint, Prettier) and continuous integration (GitHub workflows).
• Various adapters (eventstore adapters, monitoring adapters, read model adapters, etc.) and how they plug into a central runtime.
Elements
– A third style for adapter/integration components.
• Annotations or legends that explain the CQRS, DDD, and event sourcing patterns within the system.
Additional Recommendations
• Be detailed – the file tree shows dozens of examples, templates, and modules; however, focus on the core architectural pillars to avoid clutter.