- Agnosticity: Of course the first principle had to be the ability to work with a cloud agnostic environment. The cloud should support concurrently running nodes that can be logged for their session and configuration and can operate from different systems. This was necessary to ensure that clouds don’t fall back to the patterns Platform as a Service (PaaS) or Infrastructure as a service (IaaS). In other words, clouds should be able to work as an abstract layer of infrastructure that just supplies all the necessary resources to the organization and the organization just has to worry about its internal business processes.
- Decomposed Software: This is one of the important principles, to have the true cloud native application. Software needs to be loosely coupled services (Microservices). These services are built around business capabilities and are independently deployable by a fully automated deployment pipeline. Independant lifecycle management per microservice is the key for adopting this principle.
- Resiliency: According to Murphy’s law — “Anything that can fail will fail”. When we apply this to software systems, In a distributed system, failures will happen. Hardware can fail. The network can have transient failures. The goal of resiliency is to return the application to a fully functioning state following a failure. One of the main ways to offer resiliency through High availability (HA) and Disaster Recovery(DR). HA and DR can be achieved through multi-node cluster, multi-region deployments.
- Flexibility: Next logical thought about such infrastructure should be its flexibility. Undoubtedly, one would expect it to be scalable. Clouds need to be flexible enough to scale up or down based on the load they are expecting to face. Having IaaS as one of the underlying infra, they can curate policies for scaling purposes. APIs can be used to control the machine images as per requirement.
- Externalized Configuration: Decoupling the configuration in the application and considering it as an artifact in versioned manner helps to eliminate the operational errors. Clouds are primarily meant to make way for automation. This means that they should be able to serve with minimal (or negligible for that matter) human intervention. The management and configuration of the services should not be an overhead for the organization being served, rather the cloud itself. That itself essentially justifies Infrastructure, Platform and even Software as a Service.

Importance of PoC in Giving Value to VCs
Over 34% of venture capitalists claim they meet their doom because their products do not fit the market. Many potential projects fail despite handsome investments, acquisitions, and mergers if not prepared. They look for gateways of opportunity. They aren't aware that...
0 Comments