Message Broker Comparison

Recently I have been given the task to find a new message broker. I was given a large list of vague requirements such as it needs to be fast, persistant, durable, etc. Below is a list that I have put together that describes a few brokers that I have researched. As I started to research more and more, I found that these are just a few of the more popular message brokers out of a very large and growing list. I you have experiance with any of these queues, or any other queues that are not mentioned here, feel free to share your thoughts.

1. RabbitMQ (AMQP)
   • Pros:
     1. Can setup retry logic using spring’s retry template
     2. Supports dynamic queue creation.
     3. JSON API to retrieve list and manage queues
     4. Web UI for queue management
     5. Very fast (10x ActiveMQ)
     6. Spring supported through Spring-AMQP package
     7. Large community support
     8. Can configure broker with exchanges/queues to manage performance and route messages based on content
     9. supports STOMP protocol
   • Cons:
     1. Broker is implemented using Erlang and not Java (impacts setup, config)
     2. AMQP is still new
2. ActiveMQ (JMS)
   • Pros:
     1. Can configure connection factory to handle retry logic (delays/redelivery)
     2. Supports dynamic queue creation.
     3. Web UI for queue management
     4. Can retrieve a list of queues through JMX
     5. Spring supported with Spring-JMS
     6. Large community support
     7. Broker is configurable through XML
   • Cons:
     1. Not as fast as RabbitMQ
     2. Messages must be sent to either queues or topics
     3. Doesn’t appear to be completely stable.
3. Qpid (AMQP)
   • Pros:
     1. Java implementation
     2. Durable queues, persistent messages using Derby DB
     3. Windows .NET SDK
   • Cons:
     1. No queue management UI, must use command line, or JMX
     2. Not completely supported by Spring. Can use Spring-AMQP, but not completely supported. NOTE: could use supported spring rabbit libraries, but would need to be using the same version of AMQP as RabbitMQ
     3. Little community support
     4. AMQP is still new
4. HornetQ (JMS)
   • Pros:
     1. Can be installed as a standalone server or with JBoss
     2. REST api to manage queues
     3. XML configuration
   • Cons:
     1. Recommended to use Java 6, although there are special client jars for Java5 (ran into issues using Java5 library)
5. ZeroMQ (AMQP)
   • Pros:
     1. Very fast
   • Cons:
     1. Queues are not durable
     2. Messages are not persistent
     3. Not really a message broker
6. WMQ (JMS)
   • Pros:
     1. Spring support
     2. Can dynamically create listeners
     3. Desktop UI management
     4. Can view messages in UI
   • Cons:
     1. Does not support dynamic queue creation (out of the box).
     2. Does not support consumer backoff (retry delay)
     3. Unless using version 7 or newer, wmq libraries does not support a way to get a current list of queues. We would need to keep track of the queues ourselves.

Getting started with Appcelerator

A few days ago I started looking into Appcelerator Titanium, which enables you to develop mobile applications for a multiple platforms using Javascript.  If you already have knowledge developing in Javascript, now you can use that knowledge to create native applications for the IPhone and Android.  Appcelerator does this by taking the javascript that you write, and compiling it into code that is supported by each specific platform.  This takes out a lot of the rework usually needed when creating applications on multiple platforms, although it still enables you to add functionality that is specific to each platform.

If you jump over to the Appcelerator web site, you will find a ton of information.  I would advise reading some of the documentation to get a feel for what is actually going on.  Appcelerator provides their own IDE which you will need to use in order to develop applications, and in order to get the IDE, you will need to create an Appcelerator account.

The next step is to install each platform's SDK if you have already not done so in the past.  When you launch the IDE, the dashboard that is displayed will show you what SDK versions are required depending on the platform that you are developing for.  

I ran into a few issues here. First of all it said that I already have xcode installed (which I do) and that I am ready to develop IPhone apps.  After creating a new project and running it, I found out that I am not ready to develop IPhone apps.  It turns out that you need the newest version of xcode in order to use Appcelerator, and depending on your version of OSX, you might not be able to get it.  The newest version of xcode is version 4, which requires OSX Lion.  So, even though Appcelerator doesn't state it, you will need to update to Lion and then update xcode to version 4.  At this point you will be ready to develop IPhone apps.

If you do not plan on building IPhone apps, but instead your cup of tea is Android, you might also run into a few problems.  On Appcelerator's dashboard, the Android tab stated that I need to update to a newer version of the SDK, but when I clicked on the update SDK button, nothing happened.  It seems to have been an issue with the IDE.  I then went on a path of trying to figure out how to update the SDK.  This was a little tough since most of the Google documentation assumes you are using Eclipse.  I ended up going into Eclipse and updating the SDK from there.  Then I went back into Appcelerator and pointed it to my newly updated version of the SDK.  

After all of the setup I was finally able to develop native applications, now all I needed was a way to learn how to do that.

After a little Googling, I found a great starter tutorial on mobile tuts. I would advise you to check it out here.

The tutorial is pretty good, it walks you through how to make a simple twitter client that loads a user's tweets into a list.

The tutorial was informative, but when I was done, I wanted to be able to add a 'refresh' button in order to refresh the tweets.  In order to accomplish this, I added a button to the top of the tabView and then added a click event to it so that when the user clicked on it, I could refresh the list.

var refreshBtn = Titanium.UI.createButton({
 title: "refresh",
 top:0,
 height:40
});

refreshBtn.addEventListener('click', function(){
 Titanium.API.log('user clicked refresh');
 loadTweets();
});

As you can see, I set the top to 0 and the height to 40.  This puts it at the top of the tab.  I then changed the top in the TabView to be 40 so that it starts right after the button.

If you run the application and click the refresh button, it will update the list and everything appears to be working.  If you try to scroll down the list though, you will start to see the text duplicate on each row.  This is  because you are creating a new tableView and adding it to the window each time you hit refresh.  In order to get around this, you need to move the creation of the TableView outside of the loadTweets function.  Then inside of the function, use tableview.setData(rowData); to update the table with the new data.

var tableView = Titanium.UI.createTableView({
   top:40
  });
...

function loadTweets(){
...
      tableview.setData(rowData);
...
}

Now when you run the application and hit the refresh button, the rows are updated and not created on top of each other.

The documentation on the Appcelerator web site is not the greatest when it comes to starting out for the first time.  Their site recommends that you download their sample project 'kitchenSink' which contains a ton of examples.  It is overwhelming at first, but if you know what you are looking for, it can be very helpful.  I used the 'button.js' example to determine out to create buttons and add events to them, and then used the 'table_refresh.js' example to determine how to refresh the list.

Getting started with Appcelerator might be a rocky road, but it definitely looks promising.

Bouncy Castle Decryption - Illegal Key Size

Recently I was asked to implement a solution that decrypts a PGP encrypted ZIP file.  I had never worked with encryption/decryption in Java before, but the task seemed simple enough. I found Bouncy Castle, fished though the API, which us loaded with examples, and poof, I was ready to test.

This is where I ran into a problem.  I received an 'Illegal Key Size' error. I turned to Google and found an answer on StackOverflow 

It turns out that the decryption provider I was using, JCA, cannot handle secret keys greater than 128 bits. The solution is to download updated JAR files from oracle and add them to our JRE.  This isn't really the best solution since I would rather not touch my installation of Java.

At this point I turned back to the API to look for a better solution. This is where I found a better solution. The trick is to remove the dependency on JCA altogether by replacing the decryptor factory as below.
Replace:

InputStream clear = pbe.getDataStream(new JcePublicKeyDataDecryptorFactoryBuilder().setProvider(SECURITY_PROVIDER).build(sKey));

with:

InputStream clear = pbe.getDataStream(new BcPublicKeyDataDecryptorFactory(sKey));

Success. No need to tweek your Java installation.

References:
http://www.javamex.com/tutorials/cryptography/unrestricted_policy_files.shtml
http://stackoverflow.com/questions/6481627/java-security-illegal-key-size-or-default-parameters