Linxter ISB Architecture

in

The Linxter SDK encapsulates all the details of how to communicate with the Linxter Internet Service Bus (ISB). Both the Linxter SDK and Linxter ISB are designed using the principles of Service Oriented Architecture. The Linxter ISB is a collection of back-end services, including:

  • The registration service handles program instance registration and re-issue of registration tokens.
  • The inbound service handles messages sent by your program instances to other program instances.
  • The outbound service is where your program instances retrieve messages that are addressed to them.
  • The object store service handles the transfer of file attachments.
  • The hostname service manages the addresses used by program instances for calling services.

The services are designed to be autonomous, interoperable, and scalable. Location transparency is another important aspect, allowing multiple data centers to be set up around the globe, with various kinds of redundancy.

The specific location of the services is not important, and may change over time based on the loads and security needs of the back-end systems. All of the addresses are managed internally by the Linxter SDK so you, as an application developer, do not have to worry about it.

Below is a high-level illustration of the Linxter ISB architecture: Linxter Internet Sevice Bus