How LBM Differs from Other Messaging Products and Potential Benefits

Robert A. Van Valzah

February 2008

[ Split HTML / Single HTML / Single PDF ]

Table of Contents
1. Introduction
2. Architectural Differences
3. Reliable Multicast Differences
4. Messaging API Differences
5. Company Differences
6. Performance Differences
7. Different Features
8. Summary and Conclusion

Abstract

This paper explains how our LBM messaging product differs from others in the marketplace and the benefits that result from these differences. Reports from existing 29West customers indicate the benefits of these differences. This paper groups these differences and presents them roughly in order of decreasing benefit to our average customer.

Disclaimers. 1) We know our own products well, but have an incomplete knowledge of other products. 2) The benefits you experience from LBM may be different from those of our existing customers.

1. Introduction

Each of the following sections is named for a potentially significant product difference between LBM and other messaging systems. Each section provides the following: our current understanding of other messaging systems; how LBM is different from them; a description of the potential benefits that the difference provides.

Because the sections are self-contained, you can move among them or read them in the order you choose without losing meaning. We often provide links between sections and to other documents to point you to related topics.

Different audiences may have different areas of interest. For example: Application Developers might want to start with Section 4 on API differences. Network Administrators can focus first on Section 3 describing reliable multicast differences and Section 7.7 on our gateway. System Architects could consider Section 2 which describes architectural differences. Managers are invited to scan the whole document lingering on "benefits" and noting the discussion in Section 5 of how 29West differs from other messaging vendors.

		Next
		Architectural Differences