... | ... | @@ -5,11 +5,12 @@ Validate _multiple_ *publishers* (aka. producers) and _multiple_ *consumers* wor |
|
|
# Best practice?
|
|
|
|
|
|
How does the best practice deployment look like?
|
|
|
|
|
|
* Have one broker accessibly via VPN (or other means of network layer security) for pure internal use and one for public / cloud?
|
|
|
* Only one broker instance serving internal as well as public / cloud work load - and if, what kind of security mechanisms are available (authentication / authorization)?
|
|
|
|
|
|
# Birds eye view [mermaid](https://mermaidjs.github.io/) diagram
|
|
|
|
|
|
Se
|
|
|
~~~ mermaid
|
|
|
graph LR
|
|
|
subgraph Cloud
|
... | ... | @@ -230,11 +231,13 @@ graph LR |
|
|
# Scenario 6 - Queue instance not available
|
|
|
|
|
|
Questions:
|
|
|
|
|
|
* What happens if the queue is not available?
|
|
|
* What are the concepts/available options in regards to business continuity and (high) availability?
|
|
|
* Start up stress test: Broker was down, but during start up, producer continuously tries to send messages.
|
|
|
|
|
|
Testing:
|
|
|
|
|
|
* The producers shall try to send the messages continuously, until the message has been accepted by the broker.
|
|
|
|
|
|
## Script
|
... | ... | @@ -244,6 +247,7 @@ TBD: Shall the script keep trying to send messages or not? |
|
|
# Scenario 7 - Message producer/consumer not available
|
|
|
|
|
|
Questions:
|
|
|
|
|
|
* Which information is stored in the message queue if subscribers have not been able to pick up messages?
|
|
|
* Can we report such situation automatically in a dashboard or via e-mail? Especially in cases where a messages haven't been picked up within their [TTL](https://en.wikipedia.org/wiki/Time_to_live)
|
|
|
|
... | ... | |