The origin of cloud computing was the result of evolution in grid computing technologies. Former Google CEO Eric Schmidt, in late gave prominence to the word cloud computing. The birth of cloud computing is even though a recent phenomenon, its root belong to some old ideas with new business, technical and social perspectives.
And speaking from the architectural point of view, cloud is organically build on an existing grid based architecture that uses the grid services and adds some technologies like virtualization and some business models.
These days, many enterprises are paying the desired attention to cloud computation and are interested in emerging cloud solutions for enterprises, especially Amazon Web Services, which still leads the thinking in the public cloud.
With Amazon, Google, and Microsoft constantly pushing the cloud paradigm forward, we can see certain new technological advancements in the near future.
Policy-based cloud resource governance
A Policy-based cloud resource governance can be defined as the is the power to accommodate governing rules around cloud-based resources. This can include resources like storage, computation, security, and APIs. There are many partner-driven tech that which can be put into this category, as well as some offerings from AWS itself.
As of today, there are more than 10,000 resources that enterprises manage, hence this need to establish policy-based governance. This was not necessary when we had only 100 to 500 resources to govern.
Smart cloud management
Smart cloud management is an aspect that talks about dynamic and automated responses for management-related tasks. Some of those tasks include performance that’s falling out of the SLA ranges, cloud performance management, resource management, and cost and billing management.
While there are good existing set of tools, they can be better. This gap will soon, and most definitely be filled by AWS, Google, and Microsoft sooner rather than later.
Proactive cloud security
As the term suggests, cloud security is the ability for security systems to act dynamically by reacting to threats and breach attempts. AWS, Google Cloud, and Microsoft Azure know that advanced security is the only way that enterprises will truly trust the cloud, and they are keen on establishing best security practices, with more focus on automation and AI.
Their overall objective is to provide cloud security where workloads and data in the public cloud is heavily secure compared to workloads sitting in the enterprise datacenters. There have been many security breaches across major enterprises serving as living proof that having workloads on premises does not protect you from hackers.
Updating huge, complex bunch of software is definitely a slow and cumbersome process. This is where microservices come in, which started gaining traction around 2012. In order to make the process easy and simple, microservices breaks these monolithic apps into multiple smaller, joined services, or “modules.”
Microservices present a modular approach, with small teams updating modules as needed, independent of the full hulking application.
DevOps was established with the purpose of providing continuous delivery: CI/CD (continuous integration / continuous delivery). DevOps, too, started gaining momentum around the year 2012.. The aim of DecOps is to speed software development by getting two groups with very different worldviews to speak to one another: developers and operations managers.
Looking at developers, they are more inclined towards the artistic curve; they create things. On the other hand, operations managers are trained to rely on metrics and spreadsheets. They are exactly the opposite. However, if you have the dev team and the ops team to work together, major software updates can flow out fast enough to gain competitive advantage.