■Topic
Architecture articles
How to structure systems that last: headless WordPress and Shopify, multi-tenant SaaS, modular monoliths versus microservices, event-driven queues, and the caching and rate-limiting fundamentals behind them.
01
Architecture
System Design Fundamentals: Caching, Queues and Rate Limiting Explained
The three building blocks behind almost every scalable system, explained with diagrams and code: cache-aside vs write-through, queue back-pressure and token-bucket limiters. Read the articleMonolith vs Microservices: Why You Should Start with a Modular Monolith
Microservices solve organisational problems most teams do not have. How to structure a modular monolith with enforced boundaries so you can extract services later, if ever. Read the articleHeadless Shopify: Is It Worth the Development Time?
The ROI of building custom storefronts on the Shopify Storefront API versus Liquid themes for mid-sized merchants, from a developer who has shipped both. Read the articleEvent-Driven Architecture with Redis and BullMQ
Decouple slow work from HTTP requests. Producers, workers, retries with back-off, idempotent handlers, dead-letter queues and the order-processing flow I built for a store. Read the articleDesigning Multi-Tenant SaaS Architecture: Data Isolation, Auth and Billing
Shared schema vs schema-per-tenant vs database-per-tenant, tenant resolution middleware, row-level security in PostgreSQL, and Stripe-based plan enforcement. Read the articleWork with meBack-end & server services All articles
02
More topics
Other topics
→
Contact
Need this built for your project?
An idea, a stubborn technical problem, or a website that should be faster than it is. Tell me about it — let’s make it happen.