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 7 Next »

The requirements our message bus solution needs to satisfy

Requirement

Verified

Verification

We need persistence

(question)

 

Topics as well as simple queues should be supported

(question)

 

Messages are exchanged asynchronously

(question)

 

Transformation of data between sender and consumer is not needed

(question)

 

We need broad API support from common languages - especially Java and C#

(question)  Java
(question)  .NET

 

We need SSL support on the wire protocol

(question)

 

Message payload should be signed - so payload shout not be changed by the bus

(question)

 

High flexibility

(question)

 

Low complexity

(question)

 

The bus must be usable "out of the box", programming shold not be necessary on the server side

(question)

 

Handling of timeouts would be nice

(question)

 

Details (requirement explanation or verification details) can be written on the requirement subpages.

  • No labels