| Excerpt |
|---|
The requirements our message bus solution needs to satisfy |
| Child pages (Children Display) | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Requirement | Verified | Verification |
|---|---|---|
We need persistence | |
|
Topics as well as simple queues should be supported | |
|
Messages are exchanged asynchronously | |
|
Transformation of data between sender and consumer is not needed | |
|
We need broad API support from common languages - especially Java and C# |
|
|
We need SSL support on the wire protocol | |
|
Message payload should be signed - so payload shout not be changed by the bus | |
|
High flexibility | |
|
Low complexity | |
|
The bus must be usable "out of the box", programming shold not be necessary on the server side | |
|
Handling of timeouts would be nice | |
|
Details (requirement explanation or verification details) can be written on the requirement subpages.