When it comes to traditional configuration management tools, Chef, Puppet and others, these usually fall into the fry camp. This approach involves dynamic configuration at deployment time. Meaning, you have a server and need to configure it for the first time, including permissions, installing packages, etc.

The most basic truth here is that there is no real consensus on operating models around any of the new technology. While there are rough agreements on a few architectural principles, there is really not a lot of best practices to which companies can pin their operations.

Over the past few years, enterprises have also adopted cloud computing -- and today, major cloud providers can each point to large enterprises making significant use of their cloud computing offerings. What is less appreciated, however, is the inconsistent level of cloud adoption throughout these enterprise customers.

Since Spring Cloud is an umbrella project we have a "release train" of related updates to all the sub-projects (like with Spring Data). The 1.0.0.M2 release has updates to spring Cloud Config, Spring Cloud Netflix, Spring Cloud Bus, Spring Cloud Security and Spring Cloud CLI.

All this awesomeness doesn’t come without some conditions. Spoon takes advantage of the idea that working in a terminal with tmux is low latency & easily shared. There is some work being done to use VNC inside spoon to allow for the use of GUI apps but that’s not the optimal use case.