Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

The requirements our message bus solution needs to satisfy


  • 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









  • No labels