--- title: Implementing Domain-Driven Design with KurrentDB: An... description: Vaughn Vernon, author of Implementing Domain-Driven Design (IDDD), presents a TypeScript reimplementation of the AgilePM example using KurrentDB as the event... canonical: https://daily.dev/posts/implementing-domain-driven-design-with-kurrentdb-an-actor-based-event-sourcing-approach-9xvd2fcal twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Implementing Domain-Driven Design with KurrentDB: An Actor-Based Event Sourcing Approach | daily.dev og:description: Vaughn Vernon, author of Implementing Domain-Driven Design (IDDD), presents a TypeScript reimplementation of the AgilePM example using KurrentDB as the event... og:url: https://daily.dev/posts/implementing-domain-driven-design-with-kurrentdb-an-actor-based-event-sourcing-approach-9xvd2fcal og:image: https://api.daily.dev/og/posts/9Xvd2FCal.png og:image:alt: Implementing Domain-Driven Design with KurrentDB: An Actor-Based Event Sourcing Approach og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Implementing Domain-Driven Design with KurrentDB: An Actor-Based Event Sourcing Approach **[Event Store](https://daily.dev/sources/eventstore)** · 35 min read · 0 upvotes · 0 comments ## Summary Vaughn Vernon, author of Implementing Domain-Driven Design (IDDD), presents a TypeScript reimplementation of the AgilePM example using KurrentDB as the event sourcing database, the DomoActors and DomoTactical open-source libraries, and Cloudflare serverless Workers. The post covers core DDD concepts including Bounded Contexts, Aggregates, CQRS, and Event Sourcing, walking through concrete TypeScript source code for the Product and BacklogItem aggregates. It explains how the Actor Model enables type-safe, asynchronous message handling, how events are persisted and state is reconstituted from KurrentDB streams, and how snapshots optimize reconstitution. The article also introduces KurrentDB enterprise features such as Kubernetes Operator, Auto-Scavenging, and Connectors, and previews upcoming installments covering CQRS projections and aggregate refactoring. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How do you implement event-sourced aggregates in TypeScript using KurrentDB? Aggregates extend an EventSourcedEntity base class that wraps a JournalAdapter actor, which calls a KurrentDBActor that in turn uses the KurrentDBClient to append events to a stream. Commands like initiate() validate input, then call apply(event), which persists the event and triggers a registered when...() callback that mutates in-memory state, both on first application and during stream reconstitution. _Developers wiring event sourcing into TypeScript services can track deeper DDD and CQRS walkthroughs on daily.dev._ ### What are DomoActors and DomoTactical libraries used for? DomoActors is an open-source TypeScript library implementing the Actor Model, supporting type-safe messaging protocols via TypeScript interfaces and dynamic proxies combined with async/await for cooperative concurrency. DomoTactical builds on it to provide DDD tactical patterns like Aggregates and Domain Events, plus built-in Event Sourcing and CQRS support through an EventSourcedEntity base class, removing the need for a separate Repository pattern. _Anyone evaluating actor-based DDD tooling in TypeScript can follow ongoing library comparisons and DDD content on daily.dev._ ### How does snapshotting work for event-sourced aggregates to avoid replaying the full event stream? A snapshot() method returns a serializable state object at a chosen version threshold, for example every 100th event version, which gets persisted alongside the event stream in KurrentDB. On reconstitution, restoreSnapshot() sets the aggregate's initial state from the snapshot, then only the trailing events since that version are replayed through the normal when...() callbacks to reach current state. _Teams tuning event-sourcing performance can find practical KurrentDB and snapshotting patterns on daily.dev._ ## Similar posts on daily.dev - [CQRS and Event Sourcing in TypeScript: A Production Walkthrough](https://daily.dev/posts/cqrs-and-event-sourcing-in-typescript-a-production-walkthrough-z0puzlhgn) · Atomic Spin · 3 upvotes · 0 comments - [Event-Driven Agent Coordination with KurrentDB: Leveraging Event Sourcing for Multi-Step Workflows](https://daily.dev/posts/event-driven-agent-coordination-with-kurrentdb-leveraging-event-sourcing-for-multi-step-workflows-chhf1nkyx) · Event Store · 1 upvotes · 1 comments - [CQRS Without the Astronaut Architecture](https://daily.dev/posts/cqrs-without-the-astronaut-architecture-pu7zqnvab) · The T-Shaped Dev · 84 upvotes · 1 comments - [Front-End Architecture with Domain-Driven Design](https://daily.dev/posts/front-end-architecture-with-domain-driven-design-pzbik3lbx) · iO tech\_hub · 139 upvotes · 11 comments --- Tags: [#architecture](https://daily.dev/tags/architecture), [#typescript](https://daily.dev/tags/typescript), [#domain-driven-design](https://daily.dev/tags/domain-driven-design) [View this post on daily.dev](https://daily.dev/posts/implementing-domain-driven-design-with-kurrentdb-an-actor-based-event-sourcing-approach-9xvd2fcal) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Implementing Domain-Driven Design with KurrentDB: An Actor-Based Event Sourcing Approach","url":"https://daily.dev/posts/implementing-domain-driven-design-with-kurrentdb-an-actor-based-event-sourcing-approach-9xvd2fcal","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/implementing-domain-driven-design-with-kurrentdb-an-actor-based-event-sourcing-approach-9xvd2fcal"},"datePublished":"2026-08-04T14:30:31.907Z","dateModified":"2026-09-14T08:31:34.892Z","description":"Vaughn Vernon, author of Implementing Domain-Driven Design (IDDD), presents a TypeScript reimplementation of the AgilePM example using KurrentDB as the event...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/2ec62a2ca423081585d5d319d357c58a?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/2ec62a2ca423081585d5d319d357c58a?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Event Store","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Event Store","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/6e7940e0a29e4b3cbfef11831ec252c2","url":"https://daily.dev/sources/eventstore"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/implementing-domain-driven-design-with-kurrentdb-an-actor-based-event-sourcing-approach-9xvd2fcal","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"architecture,typescript,domain-driven-design","timeRequired":"PT35M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Event Store","item":"https://daily.dev/sources/eventstore"},{"@type":"ListItem","position":3,"name":"Implementing Domain-Driven Design with KurrentDB: An Actor-Based Event Sourcing Approach"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/implementing-domain-driven-design-with-kurrentdb-an-actor-based-event-sourcing-approach-9xvd2fcal#faq","mainEntity":[{"@type":"Question","name":"How do you implement event-sourced aggregates in TypeScript using KurrentDB?","acceptedAnswer":{"@type":"Answer","text":"Aggregates extend an EventSourcedEntity base class that wraps a JournalAdapter actor, which calls a KurrentDBActor that in turn uses the KurrentDBClient to append events to a stream. Commands like initiate() validate input, then call apply(event), which persists the event and triggers a registered when...() callback that mutates in-memory state, both on first application and during stream reconstitution. Developers wiring event sourcing into TypeScript services can track deeper DDD and CQRS walkthroughs on daily.dev."}},{"@type":"Question","name":"What are DomoActors and DomoTactical libraries used for?","acceptedAnswer":{"@type":"Answer","text":"DomoActors is an open-source TypeScript library implementing the Actor Model, supporting type-safe messaging protocols via TypeScript interfaces and dynamic proxies combined with async/await for cooperative concurrency. DomoTactical builds on it to provide DDD tactical patterns like Aggregates and Domain Events, plus built-in Event Sourcing and CQRS support through an EventSourcedEntity base class, removing the need for a separate Repository pattern. Anyone evaluating actor-based DDD tooling in TypeScript can follow ongoing library comparisons and DDD content on daily.dev."}},{"@type":"Question","name":"How does snapshotting work for event-sourced aggregates to avoid replaying the full event stream?","acceptedAnswer":{"@type":"Answer","text":"A snapshot() method returns a serializable state object at a chosen version threshold, for example every 100th event version, which gets persisted alongside the event stream in KurrentDB. On reconstitution, restoreSnapshot() sets the aggregate's initial state from the snapshot, then only the trailing events since that version are replayed through the normal when...() callbacks to reach current state. Teams tuning event-sourcing performance can find practical KurrentDB and snapshotting patterns on daily.dev."}}]} ```