Skip to content
SparkTime, home

Tagged #microservices

GuideTechnology

16 min read

Design an E-Commerce System: Catalog, Cart, Checkout, Inventory and Flash Sales

Design an online store from product pages to delivery: a catalogue and search served from caches and event-fed indexes, carts in a key-value store, inventory reservations with expiry, a checkout saga across inventory and payment, oversell prevention, and a flash sale that survives a thousandfold spike with a waiting room, bucketed stock and isolation from normal shopping.

GuideTechnology

17 min read

Design a Food Delivery Platform: Orders, Restaurants and Delivery Partners

Design a food delivery platform where every order coordinates three parties in real time: restaurant discovery and menus as cached read models, an idempotent checkout, an order state machine driven by a saga with timeouts and compensations, dispatching delivery partners timed to food readiness, batching, live tracking, notifications, dinner-peak load, failures and the trade-offs between them.

GuideTechnology

14 min read

Event-Driven Architecture, CQRS and Event Sourcing

When services communicate by publishing facts instead of calling each other: commands versus events, event notification versus event-carried state transfer, designing and versioning events, ordering, replay, and the two patterns often paired with events: CQRS read models and event sourcing, with honest guidance on when each is worth its complexity.

GuideTechnology

14 min read

Monolith vs Modular Monolith vs Microservices: How to Choose

An honest comparison of monoliths, modular monoliths and microservices: what each gives and costs, why a modular monolith is often the best start, how to draw service boundaries and own data, synchronous versus asynchronous communication, API gateways, service discovery, service meshes, the distributed-monolith trap, and migrating with the strangler fig pattern.

GuideTechnology

16 min read

Distributed Transactions: Two-Phase Commit, the Outbox Pattern and Sagas

How to keep data consistent when one business action spans a database and a message broker, or several services. Covers the dual-write problem, the transactional outbox and change data capture, two-phase commit and why it blocks, and sagas with compensating transactions, choreography versus orchestration, pivot steps and isolation anomalies, with a runnable saga.