New technology that experiences high growth rates will inevitably attract hyperbole. Cloud computing is no exception, and almost everyone has his or her own definition of cloud from “it’s on the internet” to a full-blown technical explanation of the myriad compute options available from a given cloud service provider.
Knowing what is and what is not a cloud service can be confusing. Fortunately, the National Institute of Standards and Technology (NIST) has provided us with a cloud computing definition that identifies “five essential characteristics.”
1. On-demand self-service. A consumer [of cloud services] can unilaterally provision computing capabilities, such as server time and network storage, as needed, automatically without requiring human interaction with each service provider. This allows you to get what you want, when you want it, with little fuss.
2. Broad network access. Capabilities are available over the network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., mobile phones, tablets, laptops and workstations). Therefore anyone, anywhere can access anything you build for them.
3. Resource pooling. The provider’s computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to consumer demand. This provides economies of scale on galactic proportions.
4. Rapid elasticity. Capabilities can be elastically provisioned and released, in some cases automatically, to scale rapidly outward and inward commensurate with demand. To the consumer, the capabilities available for provisioning often appear unlimited and can be appropriated in any quantity at any time. You get what you want, when you want it … then give it back.
5. Measured service. Cloud systems automatically control and optimize resource usage by providing a metering capability as appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled and reported, providing transparency for both the provider and consumer of the utilized service. You get what you want, when you want it, then give it back but, only pay for what you use.
Each of these five characteristics must be present, or it is just not a cloud service, regardless of what a vendor may claim. Now that public cloud services exist that fully meet this cloud computing definition, you — the consumer of cloud services — can log onto one of the cloud service providers’ dashboards and order up X units of compute capacity, Y units of storage capacity and toss in other services and capabilities as needed. Your IT team is not provisioning any of the hardware, building images, etc., and this all happens within minutes vs. the weeks it would normally take in a conventional on-premise scenario.
Three ways to migrate your IBM mainframe to AWS.
Legacy Modernization is about more than just saving money by running systems in a less expensive environment.
As technology advances, mainframe organizations are increasingly pressed to transition to more modern platforms. Here are some of the most common misconceptions that hinder their mainframe modernization journey.
The cost of not modernizing mainframe systems is generally far greater than the time, effort, and money required to make the transition. Here's why.
As mainframes host mission-critical applications, it's essential to ensure that the modernization process is accurate and causes minimal disruption to business operations. This is where automated migration and testing tools come in.
Get in touch with our experts and find out how Astadia's range of tools and experience can support your team.contact us now