Join us

How We Saved $500,000 Per Year by Rolling Our Own “S3”

How We Saved $500,000 Per Year by Rolling Our Own “S3”

Nanit ditched S3’s PutObject-heavy ingest path and built a custom Rust-based in-memory landing zone (N3). It cut ~$500K/year in storage ops. N3 grabs short-lived video chunks straight into RAM and only spills to S3 when it has to. Ordering stays tight thanks to SQS FIFO, and fallback kicks in clean when traffic spikes.

Bigger move: More teams are rolling their own short-lived, in-memory infra to dodge the scaling tax of cloud pricing models that bill per request.


Let's keep in touch!

Stay updated with my latest posts and news. I share insights, updates, and exclusive content.

Unsubscribe anytime. By subscribing, you share your email with @kaptain and accept our Terms & Privacy.

Give a Pawfive to this post!


Only registered users can post comments. Please, login or signup.

Start blogging about your favorite technologies, reach more readers and earn rewards!

Join other developers and claim your FAUN.dev() account now!

Avatar

Kaptain #Kubernetes

FAUN.dev

@kaptain
Kubernetes Weekly Newsletter, Kaptain. Curated Kubernetes news, tutorials, tools and more!
Developer Influence
1

Influence

1

Total Hits

20

Posts