The MQ tutorials¶
Audience: Architects, Application developers, Administrators
In this topic we're going to:
- Introduce you to the MQ tutorials
- Outline the structure of the tutorials
By the end of this topic you'll understand the MQ tutorials, and how they can help you design and build cloud native MQ systems.
The purpose of the MQ tutorials is to teach architects, developers and operations staff how to implement a production-ready MQ deployment on the OpenShift Container Platform. It makes extensive use of the IBM Cloud Pak for Integration (CP4I) and other cloud native technologies such as Tekton, Kustomize, ArgoCD, Prometheus, Grafana and Kibana.
Cloud native systems are loosely coupled, making them resilient, manageable, and observable. A cloud native systems brings robust DevOps automation which allows MQ developers, administrators and architects to make high quality changes with predictability and minimal toil as frequently as their organization requires.
Using worked examples, you will build and run a modern MQ deployment according to cloud native principles, gaining hands-on experience of these technologies and their benefits.
The tutorial is structured as a set of tutorials and it is recommended that you follow them in order. Earlier tutorials are foundational, whereas later ones such as high availability and disaster recovery cover advanced features. If you already have a good working knowledge of MQ and OpenShift, these more advanced topics can be attempted stand-alone. There is an intuitive table of contents. Next and Previous links at the bottom of each page to help you navigate.
The tutorial is intended as a complement to MQ product documentation; where relevant the tutorial will refer to it and other documents.
This tutorial is divided into chapters that help you build, step-by-step, a set of working MQ deployments, based on a cloud native approach. Each chapter comprises topics which you should complete in order to gain a full understanding. The tutorial starts with a simple MQ application and queue manager. It progresses to MQ uniform cluster, MQ NativeHA and multiple availability zone and region configurations.
The tutorial is structured to match the development and operations lifecycle:
- Install and upgrade
- Build and test
- High Availability
- Disaster recovery
- CPU, memory, network utilization
- Server consolidation
See how the table of contents on the left of this tutorial is arranged to match this lifecycle.
Throughout the tutorial you'll see alternative implementation choices:
Baking: Extending the official MQ image for the purpose of embedding configuration or adding third party binaries. Baking happens at build time.
Frying: Using a ConfigMap to add configuration information to an existing MQ image. Frying happens at deployment time.
The inline text gives a summary of the architecture decision used to make the technical choice. The link provides a full explanation of the architecture decision.
All architecture decisions are described in the Architecture decisions registry.