Red Hat 3scale API Management on OpenShift Demo

Red Hat 3scale API Management on OpenShift Container Platform demonstration preparation and guide.

Table of Contents

• Installation Guide

• 3scale Architecture

  • 3scale high level overview

  • 3scale basic architecture

  • 3scale basic resources

• Demo Cluster Overview

• Demo Applications

• Testing Demo Applications

• Working With 3Scale API Management (Demo)

• References

3scale Architecture

3scale high level overview

3scale overview

3scale basic architecture

3scale architecture

3scale basic resources

• Backend - represents a deployed backend application or service by pointing to its root URL.

• Product - previously called services, represent a collection of 3scale objects that pertain to a specific client or group of users. Products contain the following 3scale configuration objects:

  • Application plans - sets of access rights that allow users to define different rules for consumers of managed APIs. You can use application plans to set rate limits, enable features, resources, and methods for API users.

  • Applications - represent a client application who is consuming API(s) via API gateway.

  • A map of backends to applications

  Note that backends do not belong to a product. This is because the same backend can be associated with several different products. Different products do not need separate backends for the same underlying API.

3scale resources

Demo Cluster Overview

Once you've done all installation steps, the overview of OpenShift cluster will be like this.

demo cluster

Demo Applications

The applictions used for demo are forked from projects created by the clever people out there. All credits are given to the project owners.

• Sample Quarkus Microservices

• Sample SOAP Spring Boot microservice

Testing Demo Applications

Follow this guide for how to test the demo applications.

Working With 3Scale API Management (Demo)

1. Onboarding new API consumer

2. Expose legacy (SOAP) API to outside world

3. More secure and flexible with API Key-pair

4. Limit API calls using Rate Limit

5. Secure your API with OpenID Connect OAuth 2.0 standard

6. Running Self-Managed API Gateway on OpenShift

7. Running Self-Manage API Gateway on VM

8. Access Control based on IP Address

TODO

• Multi-Environments management guideline

• API as Code, CI/CD pipeline (Tekton + ArgoCD)

• 3scale setup using NFS server running in the same cluster

References

• DO240 - Cloud-native API Administration with Red Hat 3scale API Management course. (Public, RedHatter)