By Raj Sreenivasan, Senior Director of Product Strategy, CA Technologies
Remember this parable? Two cats were fighting over a cake. A passing monkey ate the cake while the cats argued. So both cats ended up with nothing. I’ve remembered this story when I’ve witnessed cloud and on-prem IT teams argue that their approach is best.
Your business is too valuable and too unique for a binary, winner-takes-all approach. Now there’s a third way that offers the best of both worlds for your business: Cloud Services. This approach is especially appealing to businesses that only use their mainframe for selective transactions and processing.
Cloud Services: what are they?
In a nutshell, Cloud Services combine the reliability, availability, scalability and high-performance computing of an on-premise mainframe, but adds cloud-like “on-demand” availability. Elements of Infrastructure-as-a-Service (Iaas), Platform-as-a-Service (PaaS) and Software-as-a-Service (SaaS) are presented as a single integrated service. And they’re available for any business that wants to design, code and deliver applications on a mainframe platform.
How do Cloud Services help you?
Cloud services deliver value because you’ll no longer need to manage the IT hardware environment and tasks that are usually handled by mainframe systems programmers. As a result, your overheads and skills risk reduce significantly. But you can still get what you need to create and maintain a mainframe environment on which you can run your applications.
Cloud Services in practice
Just as important, you’ll retain control of your most valuable mainframe assets, such as source code, databases, data sets and batch schedules. You’ll still manage and maintain processes like provisioning execution environments (both test and production) for application and database serving. And you’ll still get to connect these applications to their databases, develop code, and create safe copies of production data for application testing and release management. Transitioning to Cloud Services is relatively straightforward too. Source code, application data, batch schedule and batch output will be extracted from your current environment and maintained by your service provider. Then they’re simply exposed back to you as a set of services.
Does this option sound less risky than rewriting decades-old COBOL code for the public cloud? An appealing way to reduce your mainframe overheads with an efficient modern service? And a way to settle the cloud/on prem debate (I won’t call it a cat fight) once and for all? Then take a look at this blog by my colleague David Stokes. And learn about our first Cloud Services offer in partnership with IBM zCloud Services