<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Mira Engineering Blog</title><description>A private engineering knowledge base for durable technical decisions.</description><link>https://blogs.mira-engineering.com/</link><item><title>Domain events: From DDD history to a reliable production flow</title><link>https://blogs.mira-engineering.com/articles/domain-events-from-history-to-production/</link><guid isPermaLink="true">https://blogs.mira-engineering.com/articles/domain-events-from-history-to-production/</guid><description>Understand how Domain Events model business facts, how aggregates record and dispatch them, and how to choose the correct transaction boundary for reliable production systems.</description><pubDate>Sat, 25 Jul 2026 00:00:00 GMT</pubDate><category>architecture</category><category>distributed-systems</category></item><item><title>Circuit Breaker: Prevent Cascading Failures Before They Take Down Your Microservices</title><link>https://blogs.mira-engineering.com/articles/circuit-breaker-prevent-cascading-failures/</link><guid isPermaLink="true">https://blogs.mira-engineering.com/articles/circuit-breaker-prevent-cascading-failures/</guid><description>Design, configure, and operate circuit breakers for production HTTP dependencies with Polly v8 and Microsoft.Extensions.Http.Resilience.</description><pubDate>Sat, 25 Jul 2026 00:00:00 GMT</pubDate><category>production-engineering</category><category>distributed-systems</category></item><item><title>Transactional Outbox: Close the Dual-Write Gap Without Distributed Transactions</title><link>https://blogs.mira-engineering.com/articles/transactional-outbox-close-the-dual-write-gap/</link><guid isPermaLink="true">https://blogs.mira-engineering.com/articles/transactional-outbox-close-the-dual-write-gap/</guid><description>Persist business state and integration messages atomically, then operate an at-least-once relay with explicit deduplication, recovery, and observability.</description><pubDate>Sat, 25 Jul 2026 00:00:00 GMT</pubDate><category>distributed-systems</category><category>production-engineering</category></item><item><title>Dead Letter Queue: Quarantine Failed Messages Without Hiding Them</title><link>https://blogs.mira-engineering.com/articles/dead-letter-queue-quarantine-not-recovery/</link><guid isPermaLink="true">https://blogs.mira-engineering.com/articles/dead-letter-queue-quarantine-not-recovery/</guid><description>Operate dead-letter queues as bounded quarantine with failure classification, ownership, safe replay, and evidence that the original defect is fixed.</description><pubDate>Sat, 25 Jul 2026 00:00:00 GMT</pubDate><category>production-engineering</category><category>distributed-systems</category></item><item><title>Production Messaging Checklist: Prove Reliability Before Release</title><link>https://blogs.mira-engineering.com/articles/production-messaging-checklist/</link><guid isPermaLink="true">https://blogs.mira-engineering.com/articles/production-messaging-checklist/</guid><description>Review message identity, contracts, delivery, idempotency, ordering, resilience, observability, recovery, and ownership with evidence rather than assumptions.</description><pubDate>Sat, 25 Jul 2026 00:00:00 GMT</pubDate><category>production-engineering</category><category>distributed-systems</category></item><item><title>Idempotent Consumer: Turn Redelivery Into One Business Effect</title><link>https://blogs.mira-engineering.com/articles/idempotent-consumer-one-message-one-business-effect/</link><guid isPermaLink="true">https://blogs.mira-engineering.com/articles/idempotent-consumer-one-message-one-business-effect/</guid><description>Design message consumers that tolerate duplicate delivery without repeating database changes, payments, notifications, or downstream commands.</description><pubDate>Sat, 25 Jul 2026 00:00:00 GMT</pubDate><category>distributed-systems</category><category>production-engineering</category></item><item><title>Saga: Choose Choreography or Orchestration for Long-Running Consistency</title><link>https://blogs.mira-engineering.com/articles/saga-choreography-vs-orchestration/</link><guid isPermaLink="true">https://blogs.mira-engineering.com/articles/saga-choreography-vs-orchestration/</guid><description>Coordinate multi-service business workflows with explicit state, compensation, timeouts, and a deliberate choice between choreography and orchestration.</description><pubDate>Sat, 25 Jul 2026 00:00:00 GMT</pubDate><category>distributed-systems</category><category>architecture</category></item><item><title>Retry, Timeout, and Backoff: Bound Transient Failure Without Amplifying It</title><link>https://blogs.mira-engineering.com/articles/retry-timeout-backoff-bound-transient-failure/</link><guid isPermaLink="true">https://blogs.mira-engineering.com/articles/retry-timeout-backoff-bound-transient-failure/</guid><description>Build deadline-aware .NET resilience pipelines that retry only safe transient failures, spread load with jitter, and preserve the caller&apos;s total latency budget.</description><pubDate>Sat, 25 Jul 2026 00:00:00 GMT</pubDate><category>production-engineering</category><category>distributed-systems</category></item><item><title>Distributed Transactions: Why Two-Phase Commit Rarely Fits Microservices</title><link>https://blogs.mira-engineering.com/articles/distributed-transactions-why-2pc-rarely-fits/</link><guid isPermaLink="true">https://blogs.mira-engineering.com/articles/distributed-transactions-why-2pc-rarely-fits/</guid><description>Understand the guarantees and failure costs of two-phase commit, how .NET transactions escalate, and when local transactions plus messaging are the safer production design.</description><pubDate>Sat, 25 Jul 2026 00:00:00 GMT</pubDate><category>distributed-systems</category><category>architecture</category></item><item><title>Exactly Once Is a Myth: Define the Guarantee at Every Boundary</title><link>https://blogs.mira-engineering.com/articles/exactly-once-is-a-myth/</link><guid isPermaLink="true">https://blogs.mira-engineering.com/articles/exactly-once-is-a-myth/</guid><description>Separate broker, producer, processor, database, and business-effect guarantees so exactly-once claims become testable production contracts.</description><pubDate>Sat, 25 Jul 2026 00:00:00 GMT</pubDate><category>distributed-systems</category><category>architecture</category></item></channel></rss>