Webhooks, outbox patterns, tenant isolation, concurrency and the other design decisions that decide whether a system is safe to retry.
10 posts
Do not find out on Black Friday that your store breaks at 300 visitors. This guide shows how to load test an online store with k6, including realistic browsing, add-to-cart and checkout scenarios.
Backend Architecture 5 min read
Redis can make WordPress, WooCommerce and Magento noticeably faster, especially for pages that cannot be page-cached. Here is how to set it up correctly and avoid common mistakes.
Backend Architecture 4 min read
Your web server affects speed, caching and security. Here is an honest comparison of Nginx, Apache and LiteSpeed for WordPress and WooCommerce sites, and which one to choose when.
Backend Architecture 4 min read
How I think about Conviro’s billing architecture: subscription truth, feature access, recoverable updates and explainable decisions.
Backend Architecture 3 min read
How I approach Moventoro’s shared order lifecycle across planning, warehouse operations, drivers, tracking and administration.
Backend Architecture 3 min read
A reliable streaming response needs explicit lifecycle events, bounded buffering, upstream cancellation, and a clear policy for partial answers.
Backend Architecture 3 min read
Use an outbox to connect database changes with event publication, then address duplicate delivery, ordering, and external side effects separately.
Backend Architecture 3 min read
Build webhook receivers that verify input, accept work durably, handle duplicate deliveries, and reconcile state when events arrive late.
Backend Architecture 3 min read
Why tenant isolation must extend through database queries, caches, background jobs, retrieval, and support tooling in a SaaS application.
Backend Architecture 3 min read
A workflow can fail after its external action succeeds. Design retries around business operations, checkpoints, and explicit failure states.
Backend Architecture 3 min read
