Database Reference
In-Depth Information
More on endpoints
While working with a service-to-service interaction, messages are transmitted in the form
of XML through queues that are normally part of Microsoft Server such as MSMQ, SQL
Server such as SQL queuing, or even part of Microsoft Azure queues for cloud computing.
There are other endpoints that services use to process resources that are not part of service-
to-service communications. These endpoints are used to process commands and messages
as well, for instance, sending a file to non-NSB-hosted services, sending SFTP files to non-
NSB-hosted services, or sending web services, such as payments, to non-NSB services.
While at the other end of these communications are non-NSB-hosted services, NSB offers
a lot of integrity by checking how these endpoints were processed. NSB provides informa-
tion on whether a web service was processed or not, with or without errors, and provides
feedback and monitoring, and maintains the records through queues. It also provides saga
patterns to provide feedback to the originating NSB services of the outcome while storing
messages from a particular NSB service to the NSB service of everything that has
happened.
In many NSB services, an audit queue is used to keep a backup of each message that oc-
curred successfully, and the error queue is used to keep track of any message that was not
processed successfully.
