Architecting the Transactional Outbox for Reliable Event Delivery
A concise guide to implementing the Transactional Outbox pattern, covering atomicity, trust boundaries, monitoring, and failure handling in distributed systems.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
A concise guide to implementing the Transactional Outbox pattern, covering atomicity, trust boundaries, monitoring, and failure handling in distributed systems.
Cross-partition queries eating your RU budget? Cosmos DB's Change Feed lets you project writes into a second container with a different partition key — here's how the lease/checkpoint machinery works, a working Functions example, and the lag and idempotency traps to design for.
ShotGrid already records every change as an EventLogEntry. Here's how the shotgunEvents daemon turns that stream into auto-created tasks, why handlers must be idempotent, and when event-driven beats polling.
Stop relying on fragile webhooks for pipeline automation. Learn how the ShotGrid Event Daemon uses local state and retry semantics to guarantee event delivery.
Learn how to architect Azure DevOps Service Hooks for event-driven integrations, focusing on security tokens, failure modes, and when to move from direct pushes to asynchronous queues.
Stop polling your database for updates. Learn how to use Cosmos DB Change Feed to build low-latency, event-driven pipelines that sync downstream services in real-time.
Learn how to decouple your Azure Cosmos DB writes from downstream processing using the Change Feed and Change Feed Processor (CFP) to build scalable, event-driven architectures.
Stop polling your database for updates. Learn how to use the Cosmos DB Change Feed to build event‑driven, real‑time data pipelines with a concrete Azure Functions example.
Deciding between Pub/Sub Push and Pull subscriptions can be the difference between a scalable architecture and a system plagued by timeouts and duplicate messages.