Jeff Kao

I think when you start to learn about the world and like, I don't think people are really all that creative with naming things.

And, you know, so it's not just programmers that have problems with naming things.

It's, you know, everybody has those issues.

Right.

It is also a very wide street in Brooklyn, so we consistently have issues with people trying to figure out which Broadway we're talking about.

Right.

Yeah, and you can already see that because there are so many of these assets, the startup time does take a little bit of a hit.

So we download all these assets in parallel from S3.

And we do actually try and sort of cache these assets.

So we deploy in Kubernetes.

And generally, when we're making new releases, only a couple of things change.

Like, oh, maybe you only updated places.

So we only need to pull those changes from S3.

And so it's maybe like a couple minutes.

But really like the future of this is we want to get it to, you know, less than a minute or, or even like in, in like 30 seconds or so.

And so this is another area where I think rust and like having, and like all the work around the data infrastructure area where like a lot of like before it was like a lot of these Java services from all the Apache projects, they're all using Java.

We're seeing like a whole ecosystem of these data infrastructure pieces that

Being moved to Rust or like... And so one of those things is we do want to start to separate the storage and compute in a way that our database can start to come up right away or download the minimal amount of assets.

And the fact that we almost like memory map some of these like assets...

You can actually translate that in a pretty straightforward way with S3 because it offers a range API.