12 Factor, or Cloud Native Apps - What EXACTLY Does that Mean for Spring Developers?

Track: Microservices
Skill Level: Intermediate
Room: Room A301
Time Slot: Tue 2/16, 4:00 PM
Tags: architecture , spring , microservices , cloud

The third platform, characterized by a fluid infrastructure where virtualized servers come into and out of existence, and workloads are constantly being moved about and scaled up and down to meet variable demand, calls for new design patterns, processes and even culture. One of the most well known descriptions of these new paradigms is the Twelve Factor App (12factor.net), which describes elements of cloud native applications. Many of these needs are squarely met through the Spring Framework, others require support from other systems. In this session we will examine each of the twelve factors and present how Spring, and platforms such as Cloud Foundry satisfy them, and in some cases we’ll even suggest that responsibility should shift from Spring to platforms. At the conclusion you will understand what is needed for cloud‐native applications, why and how to deliver on those requirements.

Tom Gamble

Thomas Gamble is a technical principal at ThoughtWorks. Tom has worked in a variety of development and management roles. He’s currently enjoying contributing to open source and helping teams to deliver quality software more efficiently (while having fun).

Josh Kruck

Josh is an Advisory Solutions Architect at Pivotal Software. He is focused on enabling delivery of customer value at a sustainable pace. In his spare time he has been building operational utilities for Cloud Foundry.