| Title: | Message bus requirements | |
|---|---|---|
| Owner: | M | |
| Creator: | M | Nov 22, 2010 |
| Last Changed by: | Christian Vandel | May 31, 2011 |
| Tiny Link: (useful for email) | https://kb-dk.atlassian.net/wiki/x/boNBAQ | |
| Export As: | Word · PDF | |
Hierarchy
Children (12)
Handling of timeouts would be nice
High flexibility
Low complexity
Message payload should be signed
Messages are exchanged asynchronously
Persistent message queues and topics
The bus must be usable "out of the box", programming should not be necessary on the server side
To ensure robustness, the messaging system should support distribution among multiple physically independent servers
Topics as well as simple queues should be supported
Transformation of data between sender and consumer is not needed
Handling of timeouts would be nice
High flexibility
Low complexity
Message payload should be signed
Messages are exchanged asynchronously
Persistent message queues and topics
The bus must be usable "out of the box", programming should not be necessary on the server side
To ensure robustness, the messaging system should support distribution among multiple physically independent servers
Topics as well as simple queues should be supported
Transformation of data between sender and consumer is not needed
Labels
There are no labels assigned to this page.
| Time | Editor | |
|---|---|---|
| May 31, 2011 14:29 | Christian Vandel | View Changes |
| Migrated to Confluence 5.3 | ||
| May 31, 2011 14:29 | Christian Vandel | View Changes |
| Migrated to Confluence 4.0 | ||
| May 31, 2011 14:29 | Christian Vandel | View Changes |
| May 31, 2011 14:28 | Christian Vandel | View Changes |
| May 31, 2011 14:21 | Christian Vandel | |
Outgoing Links