Object store is quickly becoming the new core data substrate. Lets build kafka, but on s3. Lets build github, but on s3. It feels like we going to see more and more "object-store first" systems in the next few years.
I am excited about this future. Give me stateless servers and a storage bucket over having to manage systems with disks any day.
I do wonder if we will see an expansion of the s3 api to support more of these use cases. S3 added a janky file append operation to their new express-one-zone bucket type, and limited to 10k total file append operations. I wonder what else we will get in the next few years.
> Give me stateless servers and a storage bucket over having to manage systems with disks any day.
I'm working on something like this for my business, but the server is the bucket. When you shut it off, the VM data is stuffed into a bucket and restored when you want it back on.
Haven't really seen a case of VM's crashing.
Our use case is that we rent out VM's with GPUs in them (on-demand, no-reservation, billed by the minute), and the GPU rental is a lot more expensive than the disk rental. Right now, we don't have a cluster of storage in our DC, so we just delete the data.
We support API/cloud-init, so if they have regular workloads, they can just boot a VM with whatever they need.
It is then... get some storage (in progress) and let people pause their VM and pay less for disk when they don't need the GPU. Fully on-demand GPU compute. Perfect for agentic workloads where you want your agent to be able to spin up larger models on enterprise gear for when it needs it.
psanford · · focus · HN ↗
I am excited about this future. Give me stateless servers and a storage bucket over having to manage systems with disks any day.
I do wonder if we will see an expansion of the s3 api to support more of these use cases. S3 added a janky file append operation to their new express-one-zone bucket type, and limited to 10k total file append operations. I wonder what else we will get in the next few years.
latchkey · · focus · HN ↗
I'm working on something like this for my business, but the server is the bucket. When you shut it off, the VM data is stuffed into a bucket and restored when you want it back on.
Kinrany · · focus · HN ↗
latchkey · · focus · HN ↗
Our use case is that we rent out VM's with GPUs in them (on-demand, no-reservation, billed by the minute), and the GPU rental is a lot more expensive than the disk rental. Right now, we don't have a cluster of storage in our DC, so we just delete the data.
We support API/cloud-init, so if they have regular workloads, they can just boot a VM with whatever they need.
It is then... get some storage (in progress) and let people pause their VM and pay less for disk when they don't need the GPU. Fully on-demand GPU compute. Perfect for agentic workloads where you want your agent to be able to spin up larger models on enterprise gear for when it needs it.