Details
-
Task
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
None
-
None
-
None
Description
I've had conversations with various individuals (ActiveMQ users, devs) about disaster recovery, and how it has different constraints and solutions depending on the use case.
Sometimes we prioritize availability (e.g. Network of Brokers) and sometimes durability (e.g. replicated JDBC). This could be made clearer in the ActiveMQ website and documentation.