Linxter describes itself as an easy to use cloud messaging platform that works on .NET and Java platforms. Linxter enables communication, via messages, between internet connected systems over its Internet Service Bus.

On reviewing this application in January 2011, I found Linkster is not as easy to use, its documentation basic, and its quick start applications are neither: they’re not quick, nor do they start.

Lixster’s use cases focus on reliable, asynchronous messaging among distributed applications. Internet-based, distributed messaging was interesting when Linxter launched in 2008; however, much larger implementations of similar services (like Microsoft’s Azure) illustrate the difficulty in gaining acceptance of hosted solutions. Platforms like Microsoft’s Azure have limited acceptance, yet the overall market seems to be more aware of hosted, or cloud-based, applications yet seems to be unsure about how they could be used. Regardless, Linxter is available and, according to its site, several services use Linxter as a key part of their implementation.

Linxter provides its messaging capability using three components:

• An SDK
• A web-based management interface
• Linkster’s Internet Service Bus

The SDK for .NET (also available for Java) is a single DLL that developers reference to gain access to Linkster’s functionality. The web based interface serves a dual purpose of registering applications, and monitoring instances. The Linkster ISB handles message transfer between applications and is sub-divided into two parts - a local SQLLite database, and Linkster’s own infrastructure. Messages get transferred from the local SQLLite database to Linkster’s infrastructure asynchronously, provided that the sending application is running. The following image, from Linxter, provides an overview:

Linxster is a paid service (pricing starts at $5 for one million messages); however, they offer free trial access. Free access is limited to using one of several types of pre-configured applications that are designed to showcase Linkster’s functionality, its ease of use, and quick setup.

I registered with the site in January 2011 and downloaded the quick start samples. The site’s documentation pages lead you to believe that the quick start applications are well-documented since the pages include step-by-step directions that include lots of screen shots. The trick to following the directions is to follow the directions given, don’t deviate by trying to figure out what you are doing.

I started to read through the rest of the site, planning to do a more thorough review, and could not believe that this project has been around since 2008. The content reads, and is organized, like it is still being written. I ended up using Google to find pages and forum posts (!) that don’t have links on the site - an obstacle that makes it too difficult to research in a reasonable amount of time.

I followed the directions to the letter and ended up with this when running Quickstart1:

Unable to connect to SDK Database. Please ensure the LinxterSDKDB.db file is in the executable directory (or data directory if ClickOnce deployed), or you specify an explicit path when constructing the LinxterSDK object.

Ok - and this is the call to LinxterSDK’s constructor -

ILinxterMessaging m_Messaging = new LinxterSDK(@"C:\dev\LinxterQuickStarts_VS2008\CS\QuickStart1.Developer\bin\Debug\LinxterSDKDB.db");

(Edited from the original version, which does not include the path)

In the end, I did not get anything deployed, so could not get started.

I created a reminder in my calendar, for six months from now, to see if Linxter has made any progress. It leaves me wondering if the applications in the showcase are by actual clients or by Linxter’s developers (or maybe really close, and patient friends).