Bring some of the Cloud Concepts to On-Premise

Let me set the context using some interesting analogy.

If you are a person who love sports and played more than one sport, it is possible that you picked up few tricks from one sport and used it in the other. Say one loves playing chess and is prepared for next steps of the opponent by thorough analysis, the same spirit (coming from chess) can help to prepare well if you are launching a product in a competitive market.

Similarly Cloud Architectures, Concepts and SOPs have now become so matured and diverse that I couldn't stop but think that - We should take some of the "Cloud Centric Concepts" to On-Premise applications.

Yes still lot of mission critical applications, platforms and solutions "run and would continue to run" On-Premise.

Related - Advantages of Keeping Mission Critical Workloads On-Premises

List of those key Concepts are as below:

• Design for Failure - The concept of Design for Failure is often used to describe?the approach that assumes that there will be a hardware or system failure somewhere, sometime – and design applications for those failures so that recovery can be performed quickly.
• Zero Downtime Upgrade - You cannot schedule downtime for mission critical production application while performing an upgrade. The production work can continue while the upgrade processes in the background and everything is seamless.?
• Storage Costs - The cost of storage for an application can vary beyond capacity stored on accessing data, retrieval frequency and network bandwidth etc. So leveraging multiple storage options as per different use-cases can significantly help the cost.
• Dynamic Resource Allocation - Auto scaling is a technique for dynamically allocating computational resources.?Depending on the load to a server pool, the number of servers that are active will typically vary automatically as demand changes.
• Stateless - ?Stateless architectures have increasingly advocated for the use of smaller, simpler services, which help move us away from the monolithic application of the past. This, in turn, allows for easier horizontal scaling of services to deal with demand peaks.?
• Security - Security doesn't end at Intranet, Https, Firewall and Certificates. It is holistic and consists of set of policies, controls, procedures and technologies?that work together to protect systems, data, and infrastructure.
• Monitoring - Collect monitoring and operational data in the form of resource usage, logs, metrics, and events, providing you with a unified view of resources, applications, and services.
• Distributed Tracing - Distributed tracing?is the capability to track and observe service requests as they flow through distributed systems. The trace data helps to pinpoint where failures or performance issues are occurring in the system - and why.
• Business Continuity - Recovery Point Objective (RPO) and Recovery Time Objective (RTO) are two of the most important parameters. These help in choosing disaster recovery or data protection plan.?

With the help of proven technologies, modern infrastructure, relevant frameworks and tools above concepts needs to be considered as "Enterprise capabilities" for the application.

Related - Bringing the Cloud Experience to Your Mission-critical Applications

For huge enterprises, these capabilities could be must as per regulations and standards. For application providers, these capabilities enable them to become enterprise partners.

Organizations value the simplicity, self-service, and automation capabilities that this experience gives them.