Effectively reduce Microservices overhead using Kong and Rancher

Effective combinations of API Management and API Gateway patterns can reduce overhead and offer simplicity in a growing Microservices ecosystem. By using: API Management Layer to centralise cross cutting General Perimeter Functions. Such as: authentication, cross origin, throttling, caching. API Gateway layer to coordinate and aggregate downstream service calls into meaningful responses for upstream clients. Effectively reduce #Microservices overhead using @mashape Kong and @Rancher_Labs: https://t.co/cJxw5EzGuR pic.twitter.com/pjjAa5fY1b — Yun Zhi Lin (@yunzhilin) July 5, 2016 »

Reference Docker Infrastructure on Tutum

Docker is disruptive, but at the end of the day you need somewhere to deploy it. And if you are sensible you want would to do it in the cloud, even if you are a bank. Earlier in 2015 I took a punt and moved our entire Docker infrastructure from self-hosted Deis to Tutum. Tutum has since been acquired by Docker. It took me 2 days to get the initial infrastructure migrated. »

Harp to Hugo

I’ve moved my blog away from Harp to Hugo. And wrote a couple of useful tools along the way: Harp2Hugo gem to do the content conversion for meta data. Alpine Docker Hugo - available on both docker hub and quay.io My blog’s Tutum Stack and Dockerfile have been updated accordingly. Check it out if you need usage examples. I chose Hugo mainly because: has proper theme support - switch/modify themes on the fly, without hacking around your content pages. »

Docker Harp Microcontainer

I’m a strong believer in Docker Microcontainers that are not based on Ubuntu or Debian, ideally less than 100mb. I was quite inspired by errordeveloper’s minimal dockerfile-oracle-java container using BusyBox. So I set out to build a minimal container for Harp web server. Why Microcontainers? 1. There’s nothing “Micro” about deploying a 15mb MicroService onto a bloated 1GB container. 2. When you setup Continuous Integration / Delivery, your pipeline is no longer very “Continuous” when it’s stuck pulling down GBs worth of redudant images across networks. »

Jekyll to Harp

In late 2014 whilst working on AngularJS frontend apps on Herkou, I discovered and recommended Harp web server to the team. Harp is a powerful static file web server with built-in template proprocessing. It helped us eliminate much tedious build tasks and ruby gems from our static client projects. If you haven’t heard of Harp, have a read of Sintaxi’s Introducing Harp. Half a year later, I have also decided to migrate over to harp for my personal blog. »