Fastly

It was up like 18% yesterday.

Fastly, which will help to try to control the pipes, you know, on the internet, it was up big yesterday too.

All these stocks had huge days where hardware was hammered, so it was a hardware hammering and a software rally yesterday.

Today, this morning, we're kinda seeing the opposite thing happen because of the Trump Truth Storm here.

You don't have an opportunity to gracefully handle it.

So especially due to the amazing work of Jake Bailey, who you know from TypeScript Go compiler, amazing software developer and incredibly prolific contributor to TinyGo, as well as being maintainer of TypeScript Go, And also Damian Grisky from Fastly.

They're really the ones who did the vast majority of the work.

They're both team members of Time to Go and have done an incredible amount of effort in order to bring the most language compatibility and also standard library compatibility so that things do the thing you expect them to do, not just it looks like it should work, but then it doesn't.

So we started using CloudFront's API caching and we added some pretty, I mean, I don't know, specific implementations where we ensure that everybody who opens the same push notification would get the same fresh data.

And eventually we migrated from CloudFront to Fastly, which is a very kind of advanced caching and CDN network.

that allows us to do proactive cache invalidation.

So when we know that our data has changed under the hood, we send a cache invalidation to Fastly's service.

And in under, I think, 150 milliseconds, that's purged across the entire globe.

So we're always trying to tune that tension of we need to have the freshest data.

9

a.m.? Comcast and Fastly

partner to develop next generation content.

I see that headline here.

So it did have a negative in its performance.

The best performing was Fastly, Varonis.

Yeah.

Which is

any big numbers, any scale numbers, just in terms of what sort of volumes of data are we talking about? What sort of network...

I mean, we are here at a Fastly event, so I'm sure there are some questions about content serving.

And in fact, I did hear some of the numbers you were giving.

What kind of scale of operations are we talking

And that includes all types of things like extracted logs, extracted features, insights that we've gleaned, and then the regular things that run the business.

Okay, that's a lot.

What role does Fastly play in being able to serve that amount of data? And like, I guess that's the, you've given me the data footprint.

Obviously the question about the access footprint is, that's a whole other question as well.