Software Engineering and Stuff

Warning: The following essay is purely a work of fiction. Any resemblance with existing products, open-source projects or wales is pure coincidence.

Kubernetes is a container orchestration system that originated at Google, and is now being maintained by the Cloud Native Computing Foundation. In this post, I am going to dissect some Kubernetes internals—especially, Deployments and how gradual rollouts of new containers are handled.

I have recently been experimenting with Kubernetes, starting with a managed cluster.
Quickly enough, I’ve wanted to try setting up my own cluster though.

I just got married!
You know, the thing you do once in your life, where you spend a whole year (sometimes more) preparing a single day. Well, we did it!

It is common knowledge that Heroku has a fair number of Erlang components, we even published a book.
When I joined, 3 years ago, I had barely heard about it.
But as I tried to get a better grasp on how the platform works, I wanted to learn how some of those erlang components work.

For a number of months now, I’ve been wanting to learn some Erlang.
A few weeks ago, I started doing so as a pet project.

Sidekiq kind of revolutionized background job processing in ruby.
By providing very fast, threaded workers and inventing it’s own profitable Open-Source business model, it is really something to look at.

Earlier today, Heroku announced SSL Beta, a way to provide SSL on your heroku-hosted app for a much lower cost than it used to be. This is an awesome feature, entirely in line with all the changes SSL for over the past year.

Every thursday morning, we meet over tea/coffee with other people living in Toulouse. We call that event “Code & Coffee”.

I spend most of my time at Heroku working on our support tools and services; help.heroku.com is one such example. Heroku’s help application depends on the Platform API to, amongst other things, authenticate users, authorize or deny access, and fetch user data.