Cloud native use case: building an order management app
Although this diagram seems complicated with its many different boxes, what I want to highlight is that a cloud-native architecture supports building tens of different microservices that can run in many different compute environments–from virtual machines, platform-as-a-service container runtimes, or serverless functions. Typically, microservices in cloud native apps are very loosely coupled, and they are associated with each other through the use of APIs (and REST calls) and messaging technologies. In this diagram, we have multiple front-end digital channels (mobile apps, Web apps, maybe a voice-controlled device), with each communicating to their edge-of-network through a back-end-to-front-end pattern. This is a common approach to cloud-native apps that, for example, enables deploying a new version of a mobile app and the APIs that support it without necessarily iterating all other parts of the overall application backend.
The back-end-to-front-end orchestrates API calls into the various microservices below it. And, again, typically, you’d have business-logic microservices and maybe foundational-persistence or integration microservices. And then right at the back end are core, high-value, cloud-native services like an integrating database in the form of cloud or object storage or an Elasticsearch engine for doing indexing or integrating with some of the value through a blockchain network or a Watson conversation.
I’m going to create the three highlighted microservices, wire them together, and get my mobile app to click all the way through to my back-end microservices app. Let’s say we already have a products database, and we need to provide a products microservice that can integrate with that database. So first, I’ll use Spring Boot as the technology in Java to build that microservice, deploying it into a Kubernetes environment. And second, I’ll build the back-end-to-front-end in Node and Express, connecting that Node/Express app to the Spring app. Third, I’ll expose that back-end-to-front-end using API Connect to give us a robust, secure API that we can then provide through to the mobile app.
Creating the new product listing microservice
Creating a backend-for-frontend microservice and iOS app
IBM Cloud Developer Tools CLI version 2.1.4 adds deployment support for IBM Cloud Private 22.214.171.124. This version of IBM Cloud Private uses a more secure Helm for Kubernetes deployments and simplifies the cluster configuration for the client compared to prior IBM Cloud Private releases.
If you're looking to lower storage costs by compressing your data and get better query performance when querying the data in Cloud Object Storage, you may want to click to learn how to convert CSV objects to Parquet.