Database Reference
In-Depth Information
Benefits of NSB
NSB provides many components needed for automation that are only found in ESBs. ESBs
provide the following:
•
Separation of duties
: From the frontend to the backend by allowing the frontend
to fire a message to a service and continue with its processing not worrying about
the results until it needs an update. Also, you can separate workflow responsibilit-
ies by separating NSB services. One service could be used to send payments to a
bank, and another service can be used to provide feedback of the current status of
the payment to the MVC-EF database so that a user may see the status of their pay-
ment.
•
Message durability
: Messages are saved in queues between services so that if the
services are stopped, they can start from the messages saved in the queues when
they are restarted. This is done so that the messages will persist, until told other-
wise.
•
Workflow retries
: Messages, or endpoints, can be told to retry a number of times
until they completely fail and send an error. The error is automated to return to an
error queue. For instance, a web service message can be sent to a bank, and it can
be set to retry the web service every 5 minutes for 20 minutes before giving up
completely. This is useful while fixing any network or server issues.
•
Monitoring
: NSB's ServicePulse can keep a check on the heartbeat of its services.
Other monitoring checks can be easily performed on NSB queues to report the
number of messages.
•
Encryption
: Messages between services and endpoints can be easily encrypted.
•
High availability
: Multiple services, or subscribers, could be processing the same
or similar messages from various services that live on different servers. When one
server, or a service, goes down, others could be made available to take over that are
already running.
