Chris Phillips’ Blog - API, Integration and Governance

Ways to handle the DataPower quorum when there is only enough Licenses for two DataPowers.

THIS HAS BEEN UPDATED - https://chrisphillips-cminion.github.io/apiconnect/2022/10/19/APIC-DataPowerQuorum2Node0.html

Chatbots have been a current fashionable project to work on right now. An API Gateway is critical to help take the load off the main business application as well as providing a way to implement multiple Chatbot intermediaries without rewriting the business logic.

In the event that a DataPower quorum is lost the remaining DataPowers can be forced into a working quorum.

API Connect has four components, there is a requirement to deploy the DataPower Gateway to their own worker nodes in Kubernetes.

I’m often asked whether IBM API Connect supports GraphQL APIs. The short answer is “yes” but let’s have a deeper look at the topic.

This article explains how in API Connect 2018.4.1.8 you can persist additional configuration to DataPower.

This article explains the basics of error handling in APIs in API Connect 2018.

When each API Connect component looses quorums it changes how the components work.

Using CLI toolkit