Software Engineering   Operations   Observability  

How To Make Your Customers Happy, with Eaze

By Rachel Perkins  |   Last modified on December 17, 2019

"Success is a catastrophe that you have to survive." -- CJ Silverio

A couple of weeks ago I had the great pleasure of hosting CJ Silverio, Principal Engineer, and Ben Gardella, Manger of Infrastructure from Eaze for a clue- and cackling-filled webcast interview.

Despite the very "serious business" looks on our faces on the webpage ;), this in-depth discussion was full of laughter (wry and otherwise) and relatable details. For example, you can follow along with Ben during his first days at Eaze, as he discovers a kind of party no one really wants to attend:

screenshot of webcast with ben talking about "deploy party"

and what it takes for CJ's inner Malcolm Tucker (yes, Peter Capaldi was in stuff before he was in Dr. Who ;)) to come out:

CJ talks about Malcolm Tucker's potty mouth

It's a classic story of "catastrophic success" -- a service built to handle the load of delivering to patients with prescriptions for marijuana suddenly having to scale to address the massive influx of customers when California legalized recreational marijuana sales.

"It turns out that people like legal marijuana delivery just as much as they like legal pizza delivery." -- CJ

Shocking, right?

From there, you'll hear about their experiences--the pain of outages at critical times for the marijuana industry, straight talk with their partners and customers, bringing Honeycomb into the picture, and making a difficult but necessary decision to replatform while maintaining their existing service in place--which would not have been possible with Honeycomb.

Curious?

Find out how they did it--watch the webcast on demand!

eaze + honeycomb logo

 

Related Posts

Software Engineering   Culture  

The CoPE and Other Teams, Part 1: Introduction & Auto-Instrumentation

The CoPE is made to affect, meaning change, how things work. The disruption it produces is a feature, not a bug. That disruption pushes things...

Software Engineering   Dogfooding  

Destroy on Friday: The Big Day 🧨 A Chaos Engineering Experiment - Part 2 

In my last blog post, I explained why we decided to destroy one third of our infrastructure in production just to see what would happen....

Teams & Collaboration   Software Engineering   Culture  

What Makes for a 'Good' Pair Programming Session?

Software changes so rapidly that developing on the cutting edge of it cannot fall to a single person. When it comes to asynchronously disseminating information...