Chris Phillips’ Blog - API, Integration and Governance

Deployment automation is at the heart of DevOps. The purpose of this article is to explain some ground rules that must be considered to start any DevOps journey. I have seen a number of clients run into issues because they did not properly plan or consider how DevOps could be best used for their business.

Trophy Kindly Provided by UK Games Expo

The first week of June is the UK Games Expo. For the last three years I have judged the UK Star Trek Attack Wing National Championships. Sometimes these are official this year unfortunately it was not.

Five scenarios for planning a service-oriented architecture or microservices architecture

First published Published May 31, 2017 and Updated June 1, 2017

Throttling is the threshold for limiting the number of requests to a component. This threshold is important wherever an invocation chain passes through several distributed components. For example, a call passes from an API consumer through various layers of the architecture before it reaches the system of record where the server responds to the request. If throttling is not configured correctly, the infrastructure is at risk of accidental or malicious overload. By taking time to correctly design the throttling implementation, you can dramatically reduce this risk.

Thanks to August Ziesemer for helping me here

If you are using API Connect with DataPower in Production you need to have the AO License file in order send on the analytics.

However if DataPower is running in Kubernetes and the pod gets restarted the applied license is lost.

If you are not in Production the best solution to this issue is use the Non Production DataPower image.

Thanks to Reinhard Heite and Ollie Dineen

API Connect has two different APIs, the provider API and the consumer API.

The provider API is used to control artefacts from the perspective of the API Provider. The consumer API is used to control artefacts belonging to the developers consuming the APIs.

I moved to Jekyll running on Github about a month ago from medium.

Medium was reporting about 1500 page views per month, Google Analytics is now reporting 4330. I am somewhat shocked that this has tripled when I have posted the same amount as at my peak on medium. Media.net has also said i have earned $0.37. Given my overhead is close to zero, this means I am in profit.

I travel a lot for work, rough 75% of weeks I am away, often out of the country.

My kids always want to know where I am and my wife wanted a home dashboard so we can quickly check useful things.

I will do another post on the dashboard aims, objectives and architecture but today I wanted to find a way to get my location data and share it.

Like many people I write a load of blog posts that never will be published. This is because they don’t get finished or because my proof readers explain to me what I am writing is rubbish. One of the challenges I have head is how to share an article before it s published in a simple way. I have tried sharing the mark down but that doesn’t show the images. I have tried setting the date to the past so it is at the bottom of the list, however that does not hide the article.

There are many places today to run your APIs. zOS Connect and Akamai are two such examples. Though I recommend that DataPower runs all APIs, if different API Gateways are available then you may want to socialise all of your APIs throught a single shop window. However these APIs still need to be managed and socialised.