Cloud: A Metaphor of Internet

For some, the journey to the cloud starts off as a pure move from physical to virtual, resulting in a private cloud structure. For others, it is a movement to public cloud infrastructure, or even an application re-architecting to leverage platform components of a cloud solution. And yet for others, it can be a combination of all of the above, depending on the type of application, business case as well as the organization’s IT architectural roadmap.

The cloud options available today between IaaS, PaaS, and SaaS are aplenty and these enable organizations of different sizes and complexity to embrace the way that best suits them.

The Advent of Cloud-Native Architecture

As cloud has evolved from being a pure infrastructure alternative to an IaaS (Infrastructure as a Service), PaaS (Platform as a Service), and SaaS (Software as a Service), new options are now available for organizations to build applications on a cloud-native architecture.

The cloud-native architecture allows organizations to break an application into smaller parts, akin to the pieces of a jigsaw puzzle and power each of these components within a self-contained ecosystem.

Unimaginable, a few years back, this ability to componentise an overall structure and glue the parts together as and when you grow, is what will happen when cloud-native architecture becomes pervasive. Cloud solutions are able to breakdown traditionally challenging components, such as database, storage, and computing into services and wrap them around a source where net-net new design and features are being released on an infrequent basis, micro-services, and containers are few such examples of cloud-native solutions.

Cloud-native architecture has also impacted skills development of IT professionals as application development, and DevOps now have virtually no distinction. A cloud architect needs to have an eye for both aspects to achieve true success expected from his or her application.

True Utility Model

One of the key propositions of cloud was that organization can pay for just what they use. While this idea has been sold very effectively, more often it has been discovered that organizations do not know or cannot work out when not to use the cloud.

Once an organization starts using the cloud for all non-production environments, the same cloud providers should, with the same rigour, educate organizations to switch-off or turn-off usage when cloud is not required. Very few organizations know to stop using the cloud during non-peak hours, or post-office hours for their non-production environments.

Savings derived can actually be used to optimise budgets and be reinvested in innovation. This remains an area where organizations should be cautious when they start on a cloud journey; how to manage expenditure and how to be meticulous with a switch-on and switch-off approach.