Scalable computing architecture explained

Microsoft .NET technology is a popular framework for scalable computing architecture and the 'componentising' of software solutions.

This technology offers a building block approach to application development utilising XML, enabling interconnectivity as well as integration to larger applications over the Internet. The attributes of XML as a basis for a data file standard have been well documented and it is enjoying widespread acceptance both as a data interchange and storage format, including within the regulated industries. XML is a public domain, platform-neutral data formatting standard. It offers an application-independent way of representing data, however rich, using plain ASCII text.

These technologies provide a 'future-proofing' quality to the LIMS/instrument integration solution. New collectors, for example, can be embedded in the software by an instrument vendor, thereby simplifying integration with the LIMS.

Using architecture based on components rather than single larger applications facilitates customisation of collectors without affecting the whole solution. In a regulated environment, this offers significant savings in the extent of validation required to demonstrate compliance with GXPs.

By using Microsoft .NET within such an architecture, the instrument integration system can be presented to the user in different ways, via a Windows32 client or web pages. The ability for a chemist to configure instruments and review the status of instruments using PDA technology is another possibility.

By using a Web service interface to store analytical data in a LIMS as part of this architecture, the processing components can be isolated from variations in multiple LIMS implementations; an important consideration with large pharmaceutical manufacturers operating on a global basis. In brief, a Web service is simply an application that can be delivered as a network service and integrated using standard Internet technologies. Much of the strength of the Web services concept lies in the fact that it combines a simple-to-understand format with proven and well-established communications technology.

Web services are built using a group of XML standards, thereby providing complete platform independence. This allows an organisation to deploy the Web service on the server platform of its choice, and to use the Web service from any application written in any programming language.

A Web service also allows for the reuse of existing business rules within the LIMS. Organisations that have standardised on a LIMS for their laboratories will also have configured the LIMS differently for specific labs - r&d and production environments, for example. Should one of the LIMS be upgraded in this situation, no changes would be required to the instrument integration functionality. This simplifies deployment of new LIMS features, reduces validation efforts, and allows much greater flexibility than conventional LIMS deployments.

LIMS users, in fact users of any software application, will be familiar with how existing applications can mysteriously stop working when they install a new application onto their PC. This is due to conflict between the .dll files in the two applications.

By isolating applications, .NET eliminates this conflict. This means that when installing a new collector, for example, at the instrument workstation there need be no concern when using .NET component-based architecture.

This not only minimises impact on PC performance, but also reduces the amount of validation required in regulated environments.