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

The requirements our message bus solution needs to satisfy

Requirement

Verified

Verification

We need persistence

(tick)

Documentation

Topics as well as simple queues should be supported

(tick)

Tested

Messages are exchanged asynchronously

(tick)

Tested

Transformation of data between sender and consumer is not needed

(tick)

Design decision

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

(tick)  Java
(question)  .NET

Tested
?

We need SSL support on the wire protocol

(tick)

Documentation

Message payload should be signed

(question)

Design Decision

High flexibility

(tick)

Documentation

Low complexity

(tick)

Tested

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

(tick)

Tested

Handling of timeouts would be nice

(question)

 

To avoid downtime and to ensure scalability, the messaging system should support distribution among multiple physically independent servers

(tick)

Tested

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

  • No labels