06 from "effect/cluster"
Cluster, Part 4
We look at idempotency and the dual-write problem, then use idempotency keys and transactions to safely handle messages that arrive more than once.
Read the blog post
// Module of the Week
The lesser-known parts of
Effect. By Maxwell Brown.
Each module starts as a blog post, gets walked through live at Effect Office Hours, and ends up as a standalone video.
- Want a module covered? Suggest it or +1 it Vote
-
- 05 from "effect/cluster"
Cluster, Part 3
We look at at-most-once and at-least-once delivery, then use persisted messages to stop Dad losing messages when a runner crashes.
Read the blog post - 04 from "effect/cluster"
Cluster, Part 2
We write our first entity, then follow one of its messages across a cluster to see how runners agree on who owns what.
Read the blog post - 03 from "effect/cluster"
Cluster, Part 1
The first in a series on Effect Cluster. We look at the actor model and how a cluster is laid out.
Read the blog post - 02 from "effect"
RcMap
Learn how RcMap uses reference counting to share scoped resources by key across consumers, with automatic cleanup, idle time to live, and capacity limits.
Read the blog post - 01 from "effect/persistence"
PersistedQueue
Learn how Effect's PersistedQueue handles background jobs, multiple workers, locking, and retries.
Read the blog post - Intro
Introducing Module of the Week
Module of the Week is a weekly blog post that explores the lesser-known parts of Effect, one module at a time.
Read the blog post
// Vote for the next module
What should we cover next?
Loading suggestions…
// Behind the series
Maxwell Brown
Founding Engineer at Effectful Technologies
Maxwell is a core contributor to Effect, with work across Effect Cluster, the Effect CLI, and Effect AI, and runs Effect Office Hours.
// Talks & appearances
// Follow the series