▸ Tag · #messaging
Messaging & queues.
Asynchronous work: queues and brokers, pub/sub, event-driven design, dead-letter handling, batching, and back-pressure that actually holds.
-
ArchitectureScaling with RabbitMQ: why message brokers matter
Synchronous controllers are how monoliths die. RabbitMQ exchanges and queues, the strangler pattern for going async, and idempotent Laravel workers.
Read post →
-
ArchitectureSynchronous vs asynchronous communication
The technical differences between synchronous and asynchronous architectures in Laravel and Shopify, and how queues, jobs, and webhooks help you scale.
Read post →
-
ArchitectureMessage queues for heavy-duty document processing
Stop running embeddings in the request cycle. Build a document pipeline on message queues with staged workers, retries, dead-letter queues, and autoscaling.
Read post →
-
ArchitectureAPI gateway: the front door of your AI stack
Stop exposing LLM providers to your frontend. The API gateway pattern for AI apps: tenant isolation, model aliases, rate limiting, and streaming-safe timeouts.
Read post →
-
ArchitectureEvent-driven architecture with Google Pub/Sub
Decouple your services or drown in latency. Topics, fan-out, push vs pull, dead-letter queues, and idempotent consumers in a Laravel Pub/Sub blueprint.
Read post →