Does this mean that devops has failed? Not in the slightest. It means that while the unscrupulous might try to sell us devops, we can't buy it. We have to live it; change is a choice we make every day, through our actions of listening empathetically and acting compassionately.
Making thoughtful decisions about tools and architecture can help. Containers prove to be a useful boundary object, and deconstructing systems to human-scale allows us to comprehend their complexity. We succeed when we share responsibility and have agency, when we move past learned helplessness to active listening. But there is no flowchart, no checklist, no shopping list of ticky boxes that will make everything better. "Anyone who says differently is selling something", as The Princess Bride teaches us.
Part rant, part devops therapy, this talk will explain in the nerdiest of terms why CAP theorem applies to human interactions too, how oral tradition is like never writing state to disk, and what we can do to avoid sadness as a service.
Speaker works for Pivotal and co-hosts the Arrested DevOps podcast.
Trying to move from Python/Django monolith to Go Microservices.
Tribalism - who else in our vertical market is already using this?
DevOps certified: they passed kindergarten - they learned to share with the other children.
DevOps in a box: I want 800 units of DevOps delivered to my office.
If you have emphaty for other human beings and you understand what they want, then you'll have a much better chance getting them to do what you want.
If developers don't have good visibility into the way production is operating then they are just goint got be guessing.
Microservices is not about decomposition of giant balls of mud. It's about scope.
CAP theorem also applies to human interaction within a company
DevOps is a culture. It i s not something you can buy.