What is a Service?
A Nodinite Service represents one end of a communication chain and is by definition a member of a Nodinite System.
A Service in Nodinite has a unique name and contain information about the following other pre-defined properties:
- System - either the sending or receiving side of the communication chain
- Direction - one of the following
- Send - One-way send, like to a file system
- Receive - One-way receive, like from a file system
- Two-way Receive - Like a Web Service that is being called by a consumer (Request/Response)
- Two-way Send - Like a Consumer calling a Web Service, this is the outbound initiating call (Request/Response)
- None - Not set, should be avoided
- Unknown - Enough said...
Transport Contracts (log points)
Restrictions within Log Views can easily be enforced if the Service also is properly configured.
You should name a Service like this:
- SVC001 - Receive Invoices from Customer A
- SVC001 - Send monthly salary to the bank
TIP: Having a unique identifier part like SVC001 in this example makes it possible to filter a large number of Services, making the administration much simpler
With this naming convention, the notion of Services will be easier to understand and follow. There are many information elements in the examples. Transportation of messages, this is information in the Endpoints. The 'Invoice' and 'Salary' are the Message Types. In the examples you will also find out the direction for the message. The source, or destination was also mentioned; 'Customer A' and 'Bank' is the System.