160+ Services, 24 Teams, 1 Jahr

Die Cloud steht für Skalierbarkeit, Kosteneffizienz und kurzer Time to Market für neue Features. Davon will auch otto.de profitieren und trat deshalb im Sommer letzten Jahres die Migration in die AWS an.

Zunächst stellte sich die Frage, wie das Ganze organisatorisch ablaufen soll. Zentral oder dezentral? Agil oder konservatives Projektmanagement? Entschieden haben wir uns für alles gleichzeitig – eine weitestgehend dezentrale Umsetzung mit hybridem Projektmanagementansatz.

Admittedly, I was mildly shocked and a bit scared when stumbling over @ZackMaril’s recent tweet claiming Clojure was a dying language. A huge discussion was sparked and a lot has been written since. A summary can be found in Arne Brasseur’s post which also offers some good insight into the community behind Clojure. Eric Normand added another layer of abstraction today and collected some more links in this week’s Drama edition of the purelyfunctional.tv newsletter.

I share Dan Lebrero’s sentiment on Clojure. Clojure taught me lessons and introduced concepts to me  that I do not want to miss any more. First and foremost I love the built-in immutable collections. Immutability as default is a milestone in my life as a developer. I compare it to git, pair-programming, continuous integration and IntelliJ IDEA (with Cursive now, of course). There was a time when I did not even know about each of these. Now I cannot imagine to ever work without any of them.

In this post I want to emphasize another not less important aspect: Productivity. With Clojure we get a whole lot of stuff done. Seriously.