System Design Codex·41wA Quick Guide to RabbitMQ
RabbitMQ is a message broker that enables asynchronous communication between applications by acting as a middleman. Messages flow from producers to exchanges, which route them to queues based on bindings and routing keys, where consumers can process them. The system supports different exchange types (direct, topic, fanout) for various routing patterns, providing decoupling, scalability, and reliability for distributed systems.
Milan Jovanović·1yEvent-Driven Architecture in .NET with RabbitMQ
Learn how to implement event-driven architecture in .NET using RabbitMQ through a step-by-step guide. This involves setting up producers and consumers using RabbitMQ with Docker, understanding key components like queues and exchanges, and exploring different patterns such as competing consumers and fanout exchanges. The guide provides code snippets for setting up the system and tips for expanding the basic setup with advanced RabbitMQ features.
ByteByteGo·49wEP168: AI Vs Machine Learning Vs Deep Learning Vs Generative AI
Explains the hierarchical relationship between AI, machine learning, deep learning, and generative AI, with AI as the overarching field and each subsequent term representing more specialized subsets. Covers SQL query execution through database subsystems including transport, query processor, execution engine, and storage engine. Lists 20 key AI agent concepts from basic agents to multi-agent systems and swarm intelligence. Describes RabbitMQ's message broker architecture using exchanges, queues, and bindings for routing messages between producers and consumers.
Laravel News·1yLaravel Simple RabbitMQ Package
The Simple RabbitMQ package for Laravel simplifies using RabbitMQ by supporting multiple connections, easy publishing, and consumer mode. You can configure queues and exchanges via Laravel's service container and manage them in a configuration file. The package uses php-amqplib as the RabbitMQ client and offers fluent, chainable syntax for message handling.
Architecture Weekly·28wRequeuing Roulette in Event-Driven Architecture and Messaging
Explores the "Requeuing Roulette" pattern in event-driven systems, where messages are put back into queues hoping for correct ordering. While this technique can work when messages aren't causally correlated and consumers are stable, it creates risks under load: messages may be reprocessed out of order, causing race conditions and CPU waste. The pattern attempts to maintain strict ordering while maximizing throughput, but this trade-off often fails in distributed systems. Better alternatives include using message grouping features (RabbitMQ routing keys, SQS message groups, Service Bus sessions) or streaming solutions like Kafka that handle ordering through partitions. Understanding actual ordering requirements and choosing simpler solutions typically beats trying to make requeueing work reliably.