Note
In the second guest post on our blog, we welcome Dima Kotik, who contributed the SQLite Pub/Sub backend to Watermill. Please give Dima a warm welcome! 🎉
Miłosz & Robert
A DNS outage is like a flash flood. It hits you and disappears as if it were never there. “It was probably the DNS” became a meme. But, half the time, we do not know the exact cause.

ThreeDotsLabs' platform is  dedicated to providing insights and resources for software engineers and technology enthusiasts. Through articles, tutorials, and open-source projects, ThreeDotsLabs offers insights into software development best practices, design patterns, and emerging technologies. Developers can learn about building scalable architectures, microservices, and cloud-native applications to solve real-world problems effectively.

Three Dots Labs

Durable execution guarantees correct program output despite system failures. This guide demonstrates implementing durable execution in Go using SQLite and Watermill by persisting input events immediately after validation, ensuring idempotent event handlers through database constraints and deduplication, and proving atomicity with chaos engineering tests. The approach uses SQLite's persistent storage as a drop-in replacement for ephemeral backends, combined with the outbox pattern and single-transaction handlers to achieve reliable recovery from network outages, service failures, and other interruptions.

Durable Background Execution with Go and SQLite

Durable Execution Requires Immediate Input Storage

Stash the Input After Parsing and Validation