RTI Message Service: Less is More Reply

If you’ve been reading up on RTI Message Service, you’ve probably noticed that its message throughput is about an order of magnitude greater, give or take, than that of other JMS implementations. That’s pretty cool. (I led the RTI Message Service team, though, so maybe I’m biased.) It means that you can take JMS-standard technology places that you never could before. If you were thinking about buying more servers, or were wondering whether you’d have to build that new component in C to get better performance, maybe those are things you don’t have to worry about anymore.

But that’s not the subject of this post.

What you may not have noticed is that RTI Message Service is also the easiest JMS implementation to set up and administer. In fact, it requires almost no administration at all.

There are no servers or daemons you need to manage, and there are no servers or daemons that can crash and bring down your system. Just put our libraries on your classpath, set up your JNDI repository, and you’re ready to go.

That JNDI repository, by the way, is just an XML file. Edit it with any tool you want, put it wherever you want. Just point your “provider URL” to it and you’re good to go. You don’t need a separate naming service running anywhere.

It’s even easy to evaluate. Click the link, give it a shot, and let me know what you think.

Submit a comment

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s