# Overview A [[message broker]] that uses [[Java Message Service (JMS)]] or [[[Advanced Message Queuing Protocol (AMQP)]] protocols to deliver messages, rather than a log-based access pattern. This means the data is kept [[in-memory]]. # Key Considerations # Pros # Cons - Requires additional complexity in order to maintain ordering of messages # Use Cases for Traditional (in-memory) Brokers #flashcard - Use in situations where messages may be expensive to process, and you want to parallelize processing on a message-by-message basis, and where message ordering is not so important - [[Video Encoding]] - [[Design a Social Media Newsfeed]] <!--ID: 1751507777045--> # Related Topics - [[RabbitMQ]] - [[ActiveMQ]] - [[IBM MQ]] - [[AWS SQS]] - [[Azure Service Bus]] - [[Google Cloud PubSub]]