Issue #8: Japan, Failure, and Microservices

This will be another relatively light issue. I was at LinuxCon in Japan together with my colleague Wi

Gordon Haff

July 27 · Issue #8 · View online
I'm a technology evangelist at Red Hat where I deal with topics such as containers, DevOps, cloud strategy, and IoT. Those will be the primary focus of this newsletter but I'll also use it to highlight generally interesting links and to provide updates on my comings and goings. Blog:

This will be another relatively light issue. I was at LinuxCon in Japan together with my colleague William Henry and I’ve been spending the past week tooling around the (very hot and humid) Japanese countryside with stops in Kyoto, Takayama, and Kanazawa. Many temples and much good food. 
I’ll be getting my photos up in due course though I may first need to rebuild my iMac given it’s taken to needing poking, prodding, and system restores on a regular basis after OS updates and even power cycles. To be fair, this system is built on a Time Machine backup that’s made its way through a couple of different systems so there’s been a lot of opportunity for crud and other oddities to develop. Nonetheless, it’s easy to succumb to just prodding it one last time and getting on with business. But I think it’s about time to rebuild the system disk.

LinuxCon Japan
William and I were at LinuxCon to give a presentation entitled “Fail often, fail fast.”  It tied into central DevOps concepts such as experimentation, constant iteration, and having a culture that supports these types of activities.
Per the abstract, software projects were historically managed on a bet the farm model. They succeeded or they failed. And when they failed (as big software projects often did), the consequences were typically dire for, not only organizations as a whole, but for many of the individuals involved. Today, by contrast, many software and the development projects have evolved toward a much more incremental, iterative, and experimental process that takes cues from the open source model which excuses (and even rewards) certain types of failure.
This presentation talked about how failure can be turned into a positive. This includes the organizational dynamics associated with tolerating uncertain outcomes, the need to define acceptable failure parameters, and the technical means by which experimentation can be automated in ways that amplify the positive while minimizing the effect of negative outcomes.
The presentation slides linked from here. An expanded writeup is on my (rapidly expanding) to do list.
William and I also ended up backfilling a slot opened up by a no-show presenter. We gave a variant of my “Containers: Don’t Skeu Them Up (Use Microservices Instead)” talk which gets into how containers can be most effectively deployed together with new technologies and approaches – including the resource management of large clusters with diverse workloads – rather than mimicking legacy sever virtualization workflows and architectures. And how new open containerized platforms, such as OpenShift, provide integration and a place to effectively run new types of applications and application architectures (such as microservices-based ones).
What I've been reading
Serverless Architectures
Hard Forks – AVC
Did you enjoy this issue?
Thumbs up 1ae5a7bdfcd3220e2b376aa0c1607bc5edaba758e5dd83b482d03965219a220b Thumbs down e13779fa29e2935b47488fb8f82977fedcf689a0cc0cc3c19fa3c6bb14d1493b
Carefully curated by Gordon Haff with Revue.
If you were forwarded this newsletter and you like it, you can subscribe here.
If you don't want these updates anymore, please unsubscribe here.