CNCF has an official definition of cloud native technologies:
Cloud-native technologies empower organizations to build and run scalable applications in modern, dynamic environments such as public, private, and hybrid clouds. Containers, service meshes, microservices, immutable infrastructure, and declarative APIs exemplify this approach.
These techniques enable loosely coupled systems that are resilient, manageable, and observable. Combined with robust automation, they allow engineers to make high-impact changes frequently and predictably with minimal toil.
For modern application, the twelve-factor application advocacy is widely accepted. In a dynamic environment, all workloads (e.g. Pods) are ephemeral. These define our best practices when building microservices, with the goal of a loosely coupled system for resiliency, manageability, and observability. The adoption of microservices also has an impact back to the organization structure, an example of Conway’s law.
The cloud native stack looks like this:
| CI/CD | Application Architect: Microservice | Declarative API |
| Service Governance: Service Mesh | ||
| Deployment: Immutable infrastructure | ||
| Runtime: Container and Container Orchestration |
New technologies are born at an unprecedented rate in each layer. Check out what the landscape looks like today.
Read more about cloud native technologies:
- GraphQL and gRPC - Big Picture For inter-process communication at a high level, the two styles are asynchronous and synchronous styles: Asynchronous event-driven style: involving an event broker as a middle man. Synchronous request-response style: including several families of technologies: RPC (Remote Procedure Call): CORBA (Common Object Request Broker Architecture) Java RMI (Remote Method… ... Read moreGraphQL and gRPC
- Kubernetes Storage on Azure 3 of 3 – Ceph by Rook - In the last two posts, I covered the native storage options on Azure Kubernetes Service, as well as Portworx as an example of a proprietary Software Defined Storage (SDS) solution. There are also a number of open-source alternative SDS solutions. Ceph has nearly a decade of history from prior to… ... Read moreKubernetes Storage on Azure 3 of 3 – Ceph by Rook
- Kubernetes Storage on Azure 2 of 3 – Portworx - In the previous post, we have discussed built-in storage classes on Azure Kubernetes. Further to that, we will examine some third-party software defined storage (SDS) options that are compatible with Azure Kubernetes Service in this post. Then we take Portworx on Azure as an example. Although, these options are specific… ... Read moreKubernetes Storage on Azure 2 of 3 – Portworx
- Kubernetes Storage on Azure 1 of 3 – built-in storage and NFS - In the previous post, we understand that to host stateful workload, we need to manage persistent storage to the Kubernetes platform. In this post, I will explore the different storage options. These options are specific to Azure Kubernetes service. However, the principals apply to any Kubernetes platform regardless of cloud… ... Read moreKubernetes Storage on Azure 1 of 3 – built-in storage and NFS
- Intro to Ceph storage - Ceph is a unified, distributed storage system designed for excellent performance, reliability and scalability. In this post, I will introduce Ceph and explain how it stands out from traditional enterprise storage technology. Software defined storage In the realm of enterprise storage, I discussed PowerScale (Isilon) from Dell EMC, and touched… ... Read moreIntro to Ceph storage
Contact Digi Hunch for Professional Services.