Two-speed IT

by Jannik Arndt

The Problem

You’re a corporation. Your IT department is old, slow and can’t innovate. Your competitor however can. So you try what every corporation tries: Two-speed IT.

The solution

It’s easy: You take the best employees from every department, put them together, give them the highest priority and a lot of funding. Kind of like a startup, but with corporate money.

The catch

You’re a corporation. You don’t have good employees. You drove them away years ago, with your processes and hierarchies. You only have employees who suck less then the others.

The solution

You hire a bunch of consultants, so your people can tell them to innovate.

The catch

You’re a corporation, remember? You don’t have good employees. You have people who are good with processes and hierarchies. They will inevitably build the only thing they know: An old, slow department that can’t innovate, with processes, hierarchies and consultants. Also, you have deprived your actual IT department of its best employees.


This example show how to write a reactive reader for the AWS Simple Queue Service, using Scala and alpakka (respective akka streams).

While the Akka documentation is incredibly well written, it has surprisingly few images. Since I visualize concepts to remember them, here is my take on how Event Sourcing in Akka Persistence works:

Changing the password for a PostgreSQL database user involves two steps: The change in the database and the change in the application code. This blog post describes how to do this without any downtime or failed authentication tries.