ActiveMQ in Action–KahaDB

• Since 5.3
• File based
• Combined with a transactional journal
• Reliable message storage
• Recovery
• Good performance
• Good Scalability

File based

• No prerequisite for a third-party database.
• Easy to use
• Allowing ActiveMQ to be downloaded and running in literally minutes.
• The structure of the KahaDB store has been streamlined especially for the requirements of a message broker.

I am interested to take a look at the design of the KahaDB structure to see how it tries to meet the requirements of a message broker. Before that, maybe I need to understand the requirements of a message broker.

• Apache ActiveMQ ™ -- KahaDB Master Slave
• Apache ActiveMQ ™ – KahaDB
• ActiveMQ - User - KahaDB corruption
• ActiveMQ KahaDB Persistence Store Full - Stack Overflow
• KahaDB Optimization
• Apache ActiveMQ ™ -- Why do KahaDB log files remain after cleanup-

 

• The KahaDB message store uses a transactional log for its indexes and only uses one index file for all its destinations.
• The configurability of the KahaDB store means that it can be tuned for most usage scenarios, from high throughput applications (for example, trading platform), to storing large amounts of messages (for example, GPS tracking).
• <persistenceAdapter>