Check out version 2.2.28

[boriwo]

Please check out our latest version 2.2.28. A binary is available for download at

http://cmbdownloads.s3-website-us-west-1.amazonaws.com/

Main difference is that we now offer an embedded jetty option so you can work with a single jar file hosting
cns, cqs and cns worker all inside a single jvm so you don't have to deal with deploying war files any more
(see readme on github for details). This makes deployment a lot easier, in particular for "hello world" type
installations where you want to run all components on a single machine.

Also note that all Admin UI URLs are now prefixed with /webui so in order to reach the Admin UI you have to
go to http://host:port/webui/

Full list of changes from version 2.2.21 from release notes:

- added embedded Jetty option allowing to run cqs, cns and cns 
  publish workers all inside the same JVM
- added new bootstrap script cmb.sh to start embedded jetty version
- long poll ReceiveMessage() calls now reuse established TCP connections
  among api servers to distribute send notifications to improve performance
- all admin UI URLs now start with /webui to make load balancer
  configuration easier
- support WaitTime and DelaySeconds as queue attributes (so far only
  supported as parameters on SendMessage() and ReceiveMessage())
- new feature to determine number of queues and topics per user 
  (also displayed in admin UI)
- number of shards is now a queue attribute so queues can be sharded
  across any number of nodes in cassandra (so far default was 100
  for all queues and could only be changed globally)
- major performance improvement for cns topics with few subscribers 
  (typically less than 100 subscribers)
- bug fix for name prefix search for queues in admin UI for large number
  of queues

[guangyu suo]

That's greate !

May I ask some questions? After I looking at the source code, I found that cns service is dependent on cqs service, am i right ? The cns' PublishAction publishes messages to cqs queue using AmazonSQSClient,  and both Producer worker and Consumer worker are receive messages from the cqs queue, then how does the README said "CMB consists of two separate services, CQS and CNS." ?  CNS can work without CQS ?

[boriwo]

Yes, you are correct, internally cns does require cqs to function as it uses queues to distribute the fan-out work. While cns and cqs are logically two independent services, cns cannot run without cqs (but you can operate cqs in standalone mode if you wish). Will make this more explicit in the readme. Thanks for the comment.