Optimizing Twelve (12) Factor app for OpenShift

25 novembre 2015Albert T. Wong2 minutes (temps de lecture)

This post was originally written by Albert T. Wong in this blog: http://developerblog.redhat.com/2015/10/12/optimizing-twelve-factor-app-red-hat-openshift/

OpenShift Enterprise by Red Hat was designed to be application architecture agnostic. In addition to running traditional stateful and/or legacy-type workloads, OpenShift Enterprise seamlessly provides support for modern, stateless Twelve-Factor applications. This document provides a guide on how to optimize the architecture and deployment of your Twelve-Factor applications on OpenShift Enterprise.

Note: The Twelve-Factor app is a methodology for building apps in modern cloud environments. Read more athttp://12factor.net/.

Factor	Relationship
Codebase	One codebase tracked in revision control, many deploys.OpenShift Enterprise can build and deploy applications directly from their source code repositories.
Dependencies	Explicitly declare and isolate dependencies. OpenShift Enterprise allows native language dependency management systems to be used. Maven, Gem, CPAN, and more are all supported for their respective languages.
Config	Store config in the environment. OpenShift Enterprise provides multiple interfaces to inject environmental configuration data.
Backing Services	Treat backing services as attached resources. OpenShift Enterprise provides many native backing services (databases, message brokers, and more) and additionally enables developers to easily consume external services, too.
Build, release, run	Strictly separate build and run stages. OpenShift Enterprise strictly separates the build, release and run stages of the codebase and can integrate into many 3rd party build/release/run applications, enabling Continuous Integration and Continuous Deployment (CI/CD).
Processes	Execute the app as one or more stateless processes. OpenShift Enterprise natively incorporates Docker containers in its deployable units. Docker containers are stateless and portable.
Port binding	Export services via port binding. OpenShift Enterprise allows applications to directly bind to and consume ports, and expose the services they provide both internally within OpenShift as well as externally.
Concurrency	Scale out via the process model. OpenShift Enterprise allows for manual or automated scaling of applications, and can support true “web-scale” app deployments.
Disposability	Maximize robustness with fast startup and graceful shutdown. Containers come and containers go. OpenShift Enterprise’s use of containers enables both fast startup and graceful shutdown, all behind a robust set of tooling.
Dev/prod parity	Keep development, staging, and production as similar as possible. “Environments” in OpenShift enterprise only differ in name. Whether there is only production or 100 steps to production, the underlying infrastructure and application architectures don’t change.
Logs	Treat logs as event streams. OpenShift Enterprise aggregates application log data from all instances with no special handling required by the developer. Logs can be viewed via a number of different mechanisms.
Admin processes	Run admin/management tasks as one-off processes. OpenShift Enterprise provides capabilities for pre- and post-deployment hooks, as well as for cron-type jobs and other “admin/management tasks”.