Category Archives: Java

Reactive Manifesto – First Reactions

While visiting the Play Framework website, I noticed a new banner in the top right corner. Perhaps “new” isn’t correct – I’ve been almost exclusively in Node.js and Rails land for the past 6 months, so I might be behind the times on this one.

Screen Shot 2013-11-10 at 10.18.14 PM

Following the links takes us to The Reactive Manifesto. As of December 6, 2013, the manifesto has 3098 signatures, and a quick google search shows that the term is taking off pretty quickly. So, I decided to dive in for a quick read, and see what, if any changes it might suggest for my development style.

This architecture allows developers to build systems that are event-driven, scalable, resilient and responsive…
-The Reactive Manifesto

In General…

  • The manifesto seems to encourage some behaviors that I really like.  For example, event-driven systems are a big part of reactive applications.  As a concrete take-away, I certainly like the idea of using lightweight message queues as a way to decouple event publishers and subscribers.  And while we are at it, let’s stay away from clumsy, closed systems like JMS, and stick to open, Polyglot platforms like RabbitMQ and ZeroMQ.
  • Resiliency.  This is the part of the manifesto that I should probably spend the most time absorbing.  As much as I hate it, I’ve written Node.js apps in the past that would crash the whole server on uncaught errors.  The classic problem of Cascading Failure shouldn’t be nearly so prevalent.  Treating errors as “events” rather than failures makes your app way more resilient.
  • Big servers are for suckers.  I know a few Sys Admins still get their jollies from putting together big iron setups, but all the cool kids are scaling horizontally.  Multi-threaded applications, and the complex, proprietary technology behind them, is less attractive than single event-driven, non-blocking processes.   The Reactive Manifesto, at some level, is a guide for writing distributed systems that are resilient in their software design, but also targeted at the physical resiliency of cloud computing.

With My Java Developer Hat…

  • If you like developing in the Play! Framework, you’ll already like a lot of what the manifesto has to say.  No surprise, due to to fact that Typesafe seems to be the driver behind the manifesto.  In any event, a few obvious features that Play! provides for Reactive Applications
    • Play! (unless you opt-out) runs on, a asynchronous, event-driven application server, that supports Non-Blocking io.  The Reactive Manifesto (quite accurately) points out that event-driven applications will remain loosly coupled, and perform better than the syncronous, blocking, multi-threaded apps.

With My Node.js Hat…

  • Node.js developers should sign the manifesto, and be proud of the common ground they can find the with Java/Scala developers using Play!.  The event-driven, non-blocking approach works with the Node.js theory perfectly.  A couple specific things that sync up well
    • Node Streams implement a lot of functionality for fulfilling the “responsive” part of the reactive manifesto.  The current version of streams provides an intuitive interface, good backpressure controls, and resistance against overloads on traffic bursts.  If you are doing IO, and not using streams, you may be missing out on a big opportunity.
    • Callbacks, Queues, Streams, & EventEmitter all provide nice ways to keep your app asynchronous and message driven.

With My Rails Hat On…

  • This one is a little bit harder.  Don’t get me wrong, I’m 100% sure you can write reactive apps using Rails, I just don’t know that the framework encourages it as readily.
  • Unlike Play! or Node, the web server is a little more of a wild card when using Rails. Webrick, Unicorn, Thin, Puma, etc.  To my knowledge, the only one of those that supports non-blocking IO is Thin, but even that is subject to the blocking aspect of Rails.
  • EventMachine has some nice features for writing reactive, event-based ruby apps.
  • I think I’m going to have to stop there, and work on a who separate post re: Reactive Applications in Rails.

Yes, I signed.  While the manifesto smells too much like a marketing tool for Play!/Typesafe, I can’t hate on a good idea.  Read the manifesto, sign it if you like what you read, and leave me some comments if you think I’m way off base on this one.

Screen Shot 2013-11-10 at 11.35.08 PM

Java YAML Shootout – SnakeYaml vs YamlBeans

After spending a couple months developing LiveOn using the Play! Framework, I’ve grown increasingly intolerant of other Java frameworks.  While I’d used YAML before in Rails & Python, Java frameworks usually ignore YAML in favor of XML for configuration.  The creators of Play! realized that XML sucked, and implemented their dependency, database, and routing configurations as YAML.

So, in the spirit of helping spread YAML around the Java world, I’ve taken a look at a few YAML libraries.  Lets see which one stacks up as the best bet for adding YAML support to your Java project.

The contenders

Note: I’ve ommited JYaml.  While it is an early implementation, and still a useful library, it is no longer maintained by its creator, and therefore not a realistic candidate.

The full code sample can be found here:

Basic Usage  – For simple usage, its pretty much a wash.  Examples in both libraries look almost identical


public void testSimpleConfigurationLoad() throws Exception {
  InputStream input = new FileInputStream(new File("src/test/resources/simpleConfig.yml"));
  Map data = (Map) Yaml.load(input);
  assertEquals("yaml-shootout", data.get("simple"));



public void testSimpleConfigurationLoad() throws Exception {
  YamlReader reader = new YamlReader(new FileReader("src/test/resources/simpleConfig.yml"));
  Map data = (Map);
  assertEquals("yaml-shootout", data.get("simple"));

Parsing to a Bean – Once again, not much difference here.


  public void testAdvancedConfigurationLoad() throws Exception {
    InputStream input = new FileInputStream(new File("src/test/resources/advancedConfig.yml"));
    YamlConfig data = (YamlConfig) Yaml.load(input);
    assertEquals("yaml-shootout", data.simple);
    assertEquals("gmail", data.advanced.type);


  public void testAdvancedConfigurationLoad() throws Exception {
    YamlReader reader = new YamlReader(new FileReader("src/test/resources/advancedConfig.yml"));
    YamlConfig data = (YamlConfig);
    assertEquals("yaml-shootout", data.simple);
    assertEquals("gmail", data.advanced.type);

Extra Features

  • Both Libraries support serialization (with a similar, simple syntax)
  • Both Libraries support deserialization into maps, lists, and Strings
  • Both Libraries support Tags & Shortcuts
  • SnakeYaml supports YAML’s merge specification.


Here, SnakeYaml starts to get the edge.  Both SnakeYaml and YamlBeans are hosted on google code.

SnakeYaml YamlBeans
Starred By 118 users 24 users
Commiters 3 1
Google Group Messages 630 57


Well, I have to say, I’m a little disappointed in the outcome. I’d hoped for something a little more controversial when I started this experiment, but it appears that SnakeYaml & YamlBeans are both excellent yaml frameworks for java, with a lot of the same syntax. However, at the end of the day, SnakeYaml gets the edge for a larger feature set, and a much more active community

Tagged ,
%d bloggers like this: