How to build a cloud native app in 30 minutes

Share this post:

I’m one of the IBM Cloud App Service architects and have been involved in leading the team in the engineering and delivery of this tool for accelerating development of cloud native apps.

After giving an overview of app architecture and stating the game plan,  I’ll take you through video demos of creating two microservices and an iOS mobile front-end.

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

More How-tos stories

How to deliver great performance for global apps on IBM Cloud

A large telecommunications service provider in Europe wants to serve customers in Brazil from their Frankfurt, Germany location. One challenge with such large geographical distances is achieving consistently low latency in order to provide a good user experience. Another challenge is scaling the infrastructure to handle a large number of user requests during peak traffic conditions.

Continue reading

Securing your Python app with OpenID Connect (OIDC)

Some weeks back I introduced to a tutorial on how to analyse GitHub traffic. The tutorial combines serverless technology and Cloud Foundry to automatically retrieve statistics and store them in Db2. The data can then be accessed and analyzed using a Python Flask app. Today, I am going to show you how the web site is protected using OpenID Connect and IBM Cloud App ID.

Continue reading

Custom login page for App ID integration

When developing an application that integrates with App ID, the standard hosted login page has a few options to change the colours or logo. In some cases, this isn't enough and direct customisation is necessary. There exists a handy guide for a custom App ID login screen in mobile applications, however for web applications a little more effort is required.

Continue reading