Linxter is a loosely-coupled, asynchronous messaging platform built on the principles of Service-Oriented Architecture (SOA). There are three implementation options for the Linxter Internet Service Bus (ISB): Shared, Dedicated and On-Premise.

As the commercial release of Linxter nears, performance details are being requested more frequently, specifically how big messages can be and how fast they can be sent and received.

Using the Shared ISB, a message can be sent by one program instance and received by another program instance in approximately 2 seconds. It is important to note that a one-to-many message transaction takes roughly the same amount of time. For customers that require a much higher throughput rate, the Dedicated and On-Premise ISBs can support a one-to-one message transaction in approximately 2.5 milliseconds.

In regards to size, a Linxter message envelope consists of a message payload (content) and can have zero to many file attachments. Using the Shared ISB, the message content can be several hundred MBs. For customers that require larger messages, the Dedicated and On-Premise ISBs can support up to 2GBs. For the message content, developers are not constrained to any specific formatting. The message content can be sent as XML, MIME, plain text, a proprietary encoding, or even encrypted cipher text. On the Shared ISB, there will be a cumulative file attachment size limit of several hundred MBs per message. For the Dedicated and On-Premise ISBs, customers will determine this setting based on their needs.

We have increased the reliability and efficiency for file transfers by enabling chunking. This feature breaks a file attachment into a series of smaller pieces and puts them back together on the receiving end. For example, let’s say you are transferring a 100MB file, and after transmitting 70MBs you lose your Internet connection… when the connection is re-established, it picks up from where it left off, instead of starting over. This is especially important with wireless connectivity becoming the norm.

All messages meet information assurance criteria – they are secure from endpoint-to-endpoint, received in the order they were sent, reliable and durable.