While the industry has promoted a dramatic trend to build new, improved styles of architecture, there remains a gap in how to address the ongoing and continuous improvement and operation of existing enterprise IT systems alongside these new 12-factor apps.
Brad Topol explains why 12-factor apps are a natural fit for Kubernetes by design, demonstrating how Kubernetes addresses virtually all of the 12 factors for scalable web apps. Brad then takes a step back to consider how well stateful and transactional workloads that were not designed for 12-factor run within Kubernetes.
Even with purist gaps from 12-factor for traditional enterprise workloads, there are real velocity and cost-management benefits to moving stateful and transactional workloads to containers. With a container-based orchestrator like Kubernetes, all workload types can take advantage of automated DevOps release pipelines, provide rich feedback loops with canary testing, leverage better automated failure recovery in production, and provide easier visibility into the operational health of services running within Kubernetes. Leveraging a standard platform for a blend of architectural types enables an enterprise to standardize operational practices for across the board. The end result might be the right path for your enterprise to drive your digital transformation.
Brad Topol is an IBM distinguished engineer, leading efforts focused on open technologies and developer advocacy. Brad is a Kubernetes contributor, serves as a member of the Kubernetes Conformance Workgroup, and is a Kubernetes documentation maintainer. Previously, he was a member of the OpenStack Foundation board of directors, an OpenStack core contributor, and the project lead for the OpenStack Interoperability Challenge effort. Brad is a coauthor of Identity, Authentication, and Access Management in OpenStack by O’Reilly.
©2018, O’Reilly UK Ltd • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • email@example.com