How One Startup Uses Event Sourcing to Rebuild Features

Failed to add items

Sorry, we are unable to add the item because your shopping cart is already at capacity.

Add to basket failed.

Please try again later

Add to wishlist failed.

Please try again later

Remove from wishlist failed.

Please try again later

Adding to library failed

Please try again

Follow podcast failed

Unfollow podcast failed

How One Startup Uses Event Sourcing to Rebuild Features

Listen for free

View show details

Episode 52 of The Technical Co-Founder Podcast dives into event sourcing—a data architecture that treats every state change as an immutable event. Lucas and Luna explore how a real startup, order-management platform Riverbend, adopted event sourcing not for auditing but to rebuild a critical feature without a database migration. They walk through the concrete trade-offs: the append-only log that doubles as a source of truth, the replay mechanism that let them add a 'subscription pausing' feature in two weeks instead of two months, and the operational cost of event versioning when schema evolves. Lucas cites Martin Kleppmann's 'Designing Data-Intensive Applications' and contrasts event sourcing with CRUD-based approaches. The conversation also touches on CQRS (Command Query Responsibility Segregation) as a natural companion pattern, and why Riverbend chose not to use an event store like EventStoreDB but built on PostgreSQL. Listeners learn when event sourcing pays off—and when it's overkill. #EventSourcing #CQRS #SoftwareArchitecture #PostgreSQL #DataPatterns #StartupEngineering #Riverbend #MartinKleppmann #FeatureRebuild #ImmutableLog #TechDebt #EngineeringTradeoffs #BusinessAndTechnology #FexingoBusiness #BusinessPodcast #TheTechnicalCoFounderPodcast #EngineeringLeadership #DataIntensiveApps Keep every episode free: buymeacoffee.com/fexingo

No reviews yet