Selected Publications

Adoption of cloud-native application architectures is helping many organizations transform their IT into a force for true agility in the marketplace. This O’Reilly report defines the unique characteristics of cloud-native application architectures such as microservices and twelve-factor applications.

Recent Publications

Recent Posts

More Posts

I’m offering a two-day, intensive, hands-on training course at the upcoming O’Reilly Software Architecture Conference in Boston, MS. The class is entitled Cloud-Native Application Architectures with Spring and Cloud Foundry. In this class you will have the opportunity to implement an easy-to-understand storefront system (complete with product search, details, reviews, and recommendations) as a cloud-native architecture using Spring and Cloud Foundry. In addition, you’ll get hands-on exposure to the Netflix OSS family of technologies.


This article was originally published in the April 2014 issue of NFJS the Magazine. This article begins an introductory series on the Go programming language. Go is a language optimized for large-scale software engineering and is rapidly becoming the language of choice for building cloud services. It does this in a very interesting way, optimizing for simplicity rather than complexity and taking a “less is exponentially more” approach.


I’ve started curating a Microservices Reading List. It’s still work in progress, but there’s some good stuff there. Watch for more!


Microservices are often described as small, loosely coupled applications that follow the UNIX philosophy of “doing one thing well.” They have also been related to the Single Responsibility Principle, the first of the five principles making up SOLID. A microservices-based architecture is typically constructed around a set of common patterns. This set of patterns is actually consistent with all of the SOLID principles when thought of at the architectural rather than the class/module level.


The gauntlet has again been dropped in the world of cloud interoperability. The dueling factions include those asserting that competitors to Amazon’s web services (principally OpenStack) must adopt AWS’s API’s in order to remain viable, and those that believe such “API cloning” will do nothing more than stunt innovation. If you were to ask me, I’d say that we’ve seen this play out before. Remember the “Clone Wars” that began in the late 1980’s and that persisted for the better part of two decades?


Upcoming Appearances

DevNexus DevNexus
Atlanta, GA
February 22-24, 2017

No Fluff Just Stuff No Fluff Just Stuff
Minneapolis, MN
March 3-5, 2017

No Fluff Just Stuff No Fluff Just Stuff
Boston, MA
March 17-19, 2017

O'Reilly SACON O’Reilly Software Architecture Conference
New York, NY
April 3-5, 2017

No Fluff Just Stuff No Fluff Just Stuff
St. Louis, MO
April 7-8, 2017

No Fluff Just Stuff No Fluff Just Stuff
Reston, VA
April 21-23, 2017

No Fluff Just Stuff No Fluff Just Stuff
Columbus, OH
April 28-30, 2017

Devoxx UK Devoxx UK
London, UK
May 11-12, 2017

Devoxx Poland Devoxx Poland
Krakow, Poland
June 21-23, 2017

UberConf UberConf
Denver, CO
July 18-21, 2017