During my time as a the team lead of a SOA team my views on how integrations are built has continually evolved and changed. I am exposed to ideas through colleagues, online, at community events, through books and via experience. Every now and again I am asked a question in a meeting and I know the answer but I don't know how to do it justice with an explanation without going away and thinking it through. I am going to try and use this post to organise my thoughts and prepare for the next meeting!
Inplace Kong update (with downtime)
docker pull new images (Kong and Konga)
Change docker compose file
- Change Kong version
- Check ports
- Add stdout vars
- Change Konga version
- Check healthcheck makes sense
Docker Stack rm kong stack
Start up the stack again with new compose file
Mods I use:
firs Industry Replacement Set 3
OpenGFX+ Trains 3.0
OpenGFX+ Road Vehicles 0.4.1
OpenGFX+ Big GUI
We're doing a Snaplogic proof of concept and the UI is quite pretty so I thought I would write some blog posts about it. This will make a break from the normal boring badly spelled content I publish! Snaplogic works very well with JSON data in its pipelines but the integrations that we need to build make heavy use of XML. One solution is to use the XML Parser snap which will convert the XML into JSON. Unfortunately, the XML Parser failed for the first pipeline we tried in our POC!
Server block with python redirect and url rewrites
I am learning how to make a utility image which can accept python commands
I setup a test amazon mariadb database to test how connections can occur using ssl
I am working on a set of experimental microservices and I am using this common approach to address some common problems I have experienced with code versioning, API versioning and different 'environments'.