| ... | ... | @@ -2,6 +2,12 @@ |
|
|
|
|
|
|
|
Validate _multiple_ *publishers* (aka. producers) and _multiple_ *consumers* working on the same [queue](https://en.wikipedia.org/wiki/Message_queue), exchange messages via some [AMQP](https://en.wikipedia.org/wiki/Advanced_Message_Queuing_Protocol) [message broker](https://en.wikipedia.org/wiki/Message_broker) without any message [corruption](https://en.wikipedia.org/wiki/Data_corruption). Messages should only be consumed *once* by a *specific* *allowed* consumer.
|
|
|
|
|
|
|
|
## 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
|
|
|
|
|
|
|
|
```mermaid
|
| ... | ... | |
