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 »

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. »

Dropwizard Microservice Spike Pt 2 - Results

After spending several days experimenting with both Dropwizard and Rails, our Engineering team put the two frameworks to a democratic vote. Dropwizard emerged as the winner, mainly due the Java heavy skill set we currently possess. However Rails does also offer alot of advantages and interesting solutions to traditional problems. I personally really like Active Records and in an ideal Microservices world, both Dropwizard and Rails should be used side by side. »

Dropwizard Microservice Spike Pt 1 - Justifications

Recently at Apmasphere we have been attempting a series of architectural spikes. One of which was to move from a single monolithic cloud based application towards a more distributed Microservices architecture using RESTful APIs. The spike ran in parrallel: I’m in charge of the JVM stream while my collegaue heads the Ruby on Rails prototype. Container-less framework During the framework selection process I decided to rule out all war-based frameworks. »