Deploy a financial microservice on LinuxONE with a private cloud
Access a hybrid cloud architecture to simulate a retail banking application on IBM Z
The banking industry recognizes that a public cloud yields many benefits, but it is also wary of the potential for loss of control, as well as security and compliance challenges. Private clouds offer much-needed relief, allowing banks and financial institutions to leverage existing assets combined with the latest innovations and providing a DevSecOps mechanism for quickly and efficiently developing applications and deploying microservices into the legacy system. This code pattern uses a hybrid cloud architecture to deploy a banking microservice on LinuxONE. The microservice accesses a simulated retail bank on an IBM Z® Mainframe via banking APIs.
A private cloud can address the challenges faced by the banking industry by delivering a fully customizable and secure solution, including robust management. It offers the benefits of a public cloud, including rapid deployment, scalability, ease of use, and elasticity. It also provides greater control, increased performance, predictable costs, tighter security, and flexible management options. You can easily configure and customize it to fit your unique needs and security requirements.
IBM Cloud Private delivers a platform that adheres to best practices for developing microservices applications by enabling cloud-native development, including Docker containers and Kubernetes. The core platform works across private, dedicated, and public clouds, and offers a variety of open source application runtimes. Open source and IBM middleware and databases are built in, enabling enterprises to build apps quickly and securely.
This code pattern uses a hybrid cloud architecture to deploy a banking microservice on LinuxONE. The microservice accesses a simulated retail bank on an IBM Z Mainframe via banking APIs.
When you complete this pattern, you will understand how to:
- Build a Docker image from an existing application.
- Deploy a Docker image to IBM Cloud Private.
- Run the existing application using the IBM Cloud Private catalog.
- User deploys a Docker image (banking application-based microservice) to the IBM Cloud Private Docker registry.
- User configures and runs a container based on the previous Docker image from the IBM Cloud Private catalog. Once started, the application calls banking APIs published in API Connect.
- API Connect calls the back-end Z mainframe through a banking API published in z/OS® Connect EE.
- z/OS Connect EE calls the Account Management System running in CICS®. A COBOL program processes the request and returns banking data. Finally, the banking data are sent back to the microservice application.
- Discover and locally run the banking application
- Build and deploy a Docker image to IBM Cloud private
- Instantiate the banking microservice from the IBM Cloud private catalog
Ready to put this code pattern to use? Complete details on how to get started running and using this application are in the README.