Mess around software system design

README
ArchitectureTradeOffAnalysis
Conversion cheat sheet
Scenarios
Time series scenarios
- Observability
Search engine
Big data
MicroSvcs
Cache
Message queue
Traditional DB
Non-Traditional DB
Java basics
- IO
- Exception handling
Java concurrency
- Overview
- Codes
Java JVM
Server
- Nginx-[TODO]
Distributed system theories
Protocols
Statistical data structure
DevOps
- Container_Docker
- Container_Kubernetes-[TODO]
Network components
Templates
- interviewRecord
TODO

Powered by GitBook

On this page

RabbitMQ
Concepts
Persistence
Memory control
High availability
Reliability
Send reliability
Storage reliability
Consumption

Was this helpful?

Message queue

Other msg queues

RabbitMQ-TODO

PreviousActiveMQ-TODO NextRocketMQ-TODO

Last updated 3 years ago

Was this helpful?

RabbitMQ

RabbitMQ

Concepts

Persistence

Queue persistence
Message persistence
Exchange persistence

Memory control

Max memory config

High availability

Metadata replication and forward
Cluster mirrored queues
Federation plugin
Shovel plugin

Reliability

Send reliability

Definition: Message could arrive at broker successfully
- At most once: Supported. Usually not used because there might be message loss.
- At least once: Supported. There are two mechanism: Publisher confirm and transaction. The latter one is slow and seldomly used.
- Exactly once: Not supported
Publisher confirm is a mechanism to return

Storage reliability

Consumption

Storage reliability: Broker could persist the message and guarantee no loss
Consumption reliability: Message could be successfully consumed