Gradle 2.0 came out last week, and it's a pretty big move from Gradle--the first major version update they've done. With the major release comes a baseline of backwards compatibility, and a significantly simplified codebase.

To gain significant business benefits, teams must understand their IT business goals, define an appropriate SOA & API mindset, describe how to implement shared services and popular APIs, and tune governance practices.

I’m a minimalist, and I don’t like to complicate software too early and unnecessarily. And adding components to a software system is one of the things that adds a significant amount of complexity. So let’s talk about message queues.

Over the past several years JSON has become the darling of service message standards. These days you are shunned if you offer a SOAP service. The more I use JSON service though the more I question if they are really the answer.