$ recombobulate _
home / tips / ask-claude-to-implement-an-event-sourcing-pattern
89

Ask Claude to Implement an Event Sourcing Pattern

recombobulate @recombobulate · Mar 26, 2026 · Workflows
ask-claude-to-implement-an-event-sourcing-pattern

Event sourcing is one of those patterns that's conceptually clear but tricky to wire up correctly from scratch. Claude can design the whole structure for your domain.

claude "Implement a basic event sourcing setup in Laravel for a BankAccount aggregate. Include: a DomainEvent base class, AccountOpened/MoneyDeposited/MoneyWithdrawn events, an EventStore using a database table, and the BankAccount aggregate that rebuilds state by replaying events."

Claude will design cohesive, minimal classes — not a framework — keeping the core pattern clear:

class BankAccount
{
    private float $balance = 0;
    private array $recordedEvents = [];

    public static function reconstitute(array $events): self
    {
        $account = new self();
        foreach ($events as $event) {
            $account->apply($event);
        }
        return $account;
    }

    private function apply(DomainEvent $event): void
    {
        match($event::class) {
            MoneyDeposited::class => $this->balance += $event->amount,
            MoneyWithdrawn::class => $this->balance -= $event->amount,
            default => null,
        };
    }
}

Ask Claude to extend it with projections, snapshots, or a process manager once the core is solid. Build incrementally.

Event sourcing pays dividends in auditability — Claude helps you get the foundation right.

~/recombobulate $ tip --comments --count=0

Log in to leave a comment.

~/recombobulate $ tip --related --limit=3
0
Run Claude Code in GitHub Actions to Automatically Review Every Pull Request

Set up Claude Code as an automated reviewer in your CI pipeline — on every pull request, it reads the diff, checks for bugs, security issues, missing tests, and convention violations, then posts its findings as a PR comment. Your human reviewers get a head start because the obvious issues are already flagged before they look.

recombobulate @recombobulate · 1 month ago
0
Ask Claude to Build a Deployment Checklist from Your Actual Infrastructure

Before deploying, tell Claude to read your project — migrations, environment variables, queue workers, scheduled tasks, caching, third-party integrations — and generate a deployment checklist that's specific to your app. Not a generic "did you run migrations?" list, but one that knows YOUR infrastructure and catches the things YOUR deploy can break.

recombobulate @recombobulate · 1 month ago
0
Ask Claude to Generate a README from Your Actual Codebase — Not a Template

Instead of writing a README from memory or copying a template, tell Claude to read your project and generate one that's actually accurate — real setup instructions from your config, real architecture from your directory structure, real API examples from your routes, and real prerequisites from your dependency files.

recombobulate @recombobulate · 1 month ago