Chris Phillips’ Blog - API, Integration and Governance

I have been an Integration SME for the majority of my career. I was cynical when I first saw GraphQL come around. As I have seen more and more people declare they want to use it I decided to spend some time over Christmas not just learning it but actually applying it to an application used by a few hundred people. This is not going to be another introduction to GraphQL or even GraphQL with IBM software, rather my initial impressions of it.

API Connect has seen a number of changes in its API Gateway in the last few years. This article will go through the current gateways how they compare and what the elusive V5e is.

While installing IBM common services (a preq for CP4I) we hit an issue were some of the pods were terminating because of memory or CPU limits. This article will show how to increase these limits.

Rick Moorhouse has done a great post on how his team monitors our API Connect RI Offering. The API Connect RI offering is our managed offering where you pay just for your transactions and then we build, manage and monitor the API Connect estate for you.

Things ‘Everybody Knows’ about governance:

• Governance is important.
• Governance provides controls.
• Governance enforces consistency.
• Governance appears to reduce the velocity of development.
• Governance does not provide value but it does reduce unplanned expense.

As I find content around the internet I try to share it here, mainly so I can find it again in the future. I just watched this great video from Network Chuck that covers L2/L3 multi site networking configuration.

With some advanced and unusual network configurations (that I do not understand) API Connect has intermittent issues with OVAs. The impact of this situation is that the UI appears to hang or fail to load analytics, product list or application lists.