Check out our Message Medium blog to find out what’s going on in the hardware-accelerated, low-latency messaging world.
May 27, 2009 at 12:00 pm
Guaranteed messaging. Guaranteed Delivery. Durable Consumer. Reliable. Blocking. Non-blocking. Persistent. Lots of descriptors attached to the concept of guaranteed messaging.
But what does guaranteed mean? Where do the guarantees occur? Is it really a guarantee or is it just statistical? What price must I pay for a guarantee? What’s my time window for assurance? How different is a guaranteed messaging flow from a best effort flow? Are there different types of guarantees?
We’ve spent a good deal of time and R&D dollars on guaranteed messaging. Though we’ve had for some time a guaranteed connected quality of service that seamless overcomes temporary operational issues, we needed something for major outages and debilitating breaks in continuity. We opted, however, not to cobble something together that would perform like a sick dog and treat the term “guarantee” lightly. Our base architecture was designed anticipating the need to have multiple qualities of services that were unified, seamless and fully functional. Guaranteed messaging was not going to incur a tax.
Today we announced our “Real-Time Guaranteed Messaging Service” - but we claimed it was the “Industry’s First.” Why? Because it is both real-time and real-guaranteed. Together for the first time. What were our objectives?
- Give customers true assurance without the debilitating deficiencies of traditional guaranteed service
- Be the highest performing guaranteed messaging on the market
- Provide true guarantees, not statistical likelihoods
- Scale cleanly from workgroup to enterprise
- Leverage architectural differentiators that our competitors just can’t match
It’s a different market and information is far too important to implement guaranteed messaging the same old way. It’s all about the architecture. That's what drives business advantage.
=rob.ciampa
Skip navigation
