Cian Butler

We're using it in specific environments now.

We haven't rolled out 100% everywhere because of these weird edge cases we found with Docker.

And the other issue we found was about connection management to our database.

We were...

It's a big problem where you need to do some upgrades, which means we've held off and we haven't got there.

And that was the biggest things about the project that was the unknown unknowns.

We sat down and I keep saying we, there was maybe me, a principal to review my work and a manager to like sign off on it.

And set out, like, we'd leverage our end-to-end test to do stuff.

We'd use our load test to validate our request throughput and that kind of stuff.

But we never like had a plan.

And we had rollback and rollout plans.

We had rollout plans that were like, well, canary in lower environments, raise them up.

We'll do it in off regions in quiet times.

All the like following the SRE handbook of like, how do you roll out changes safely?

But we had issues with that business logic.

At the start of all this, we started pulling in Rust tools to speed up Python because we didn't want to do a full rewrite for many different reasons.

We wanted to use small bits of Rust in our stack to speed it up or small bits of C if that was going to be there as well.

we were very much just looking for faster ways to do what we were currently doing.

But what we were currently doing wasn't well, wasn't understood enough by myself and others because we have that 10 years of legacy.

There's edge cases where the person who worked on it has come and gone or that same person has come and gone to the company three times.