Introduction to Principles of Container-based Application Design

1st chunk of `content/en/blog/_posts/2018-03-00-Principles-Of-Container-App-Design.md`

4bdf76ae71acbd06f752263b992e20a42e4bd61bbaf1f3fa0000000100000457

---
title: "Principles of Container-based Application Design"
date: 2018-03-15
slug: principles-of-container-app-design
url: /blog/2018/03/Principles-Of-Container-App-Design
author: >
   [Bilgin Ibryam](http://twitter.com/bibryam) (Red Hat)
---

It's possible nowadays to put almost any application in a container and run it. Creating cloud-native applications, however—containerized applications that are automated and orchestrated effectively by a cloud-native platform such as Kubernetes—requires additional effort. Cloud-native applications anticipate failure; they run and scale reliably even when their infrastructure experiences outages. To offer such capabilities, cloud-native platforms like Kubernetes impose a set of contracts and constraints on applications. These contracts ensure that applications they run conform to certain constraints and allow the platform to automate application management.

I've outlined [seven principles][1]for containerized applications to follow in order to be fully cloud-native.   

| ----- |
|

Title: Introduction to Principles of Container-based Application Design

Summary

This section introduces the concept of container-based application design and highlights the importance of creating cloud-native applications that can run and scale reliably on platforms like Kubernetes. The author outlines seven principles for containerized applications to ensure they are fully cloud-native and can be effectively managed by the platform.