News for hackers. Stuff that matters.
Re:Systems Correctness Practices at Amazon Web Services by simonw on Friday May 30, 2025 @12:02PM (#44137548)
S3 remains one of the most amazing pieces of software I've ever seen. That thing a few years ago where they just added strong read-after-write consistency to the whole system? Incredible software engineering. https://aws.amazon.com/blogs/aws/amazon-s3-update-strong-rea...
Re:Systems Correctness Practices at Amazon Web Services by positisop on Friday May 30, 2025 @01:25PM (#44138279)
Google Cloud Storage had it for eons before S3. GCS comes across as a much better thought-out and built product.
Re:Systems Correctness Practices at Amazon Web Services by simonw on Friday May 30, 2025 @02:44PM (#44138897)
S3 is probably the largest object store in the world. The fact that they can upgrade a system like that to add a feature as complex as read-after-write with no downtime and working across 200+ exabytes of data is really impressive to me.
Re:Systems Correctness Practices at Amazon Web Services by tossandthrow on Friday May 30, 2025 @03:07PM (#44139062)
I really do respect the engineering efforts.

But object stores are embarrassingly parallel, so if such a migration should be possible somewhere without down time, then it is definitely object stores.

Re:Systems Correctness Practices at Amazon Web Services by gamegoblin on Friday May 30, 2025 @04:31PM (#44139615)
Where would you make make the cut that takes advantage of object store parallelism?

That is, at what layer of the stack do you start migrating some stuff to the new strongly consistent system on the live service?

You can't really do it on a per-bucket basis, since existing buckets already have data in the old system.

You can't do it at the key-prefix level for the same reason.

Can't do both systems in parallel and try the new one and fall back to the old one if the key isn't in it, because opens up violations of the consistency rules you're trying to add.

Seems trickier than one might think.

Re:Systems Correctness Practices at Amazon Web Services by nojvek on Friday May 30, 2025 @08:48PM (#44141078)
Obviously depends on how they delivered read after write.

Likely they don't have to physically move data of objects, but the layer that writes and reads coordinates based on some version control guarantees e.g in database land MVCC is a prominent paradigm. They'd need a distributed transactional kv store that tells every reader what the latest version of the object is and where to read from.

An object write only acknowledges finished if the data is written and kv store is updated with new version.

They could do this bucket by bucket in parallel since buckets are isolated from each other.

Re:Systems Correctness Practices at Amazon Web Services by SteveNuts on Friday May 30, 2025 @01:53PM (#44138511)
Sure, but whose (compatible) API is GCS using again? Also keep in mind that S3 is creeping up on 20 years old, so backing a change in like that is incredible.
Re:Systems Correctness Practices at Amazon Web Services by benoau on Friday May 30, 2025 @01:55PM (#44138530)
Not just 20 years old - an almost flawless 20 years at massive scale.
Re:Systems Correctness Practices at Amazon Web Services by SteveNuts on Friday May 30, 2025 @02:16PM (#44138699)
It's funny that things that are pinnacles of human engineering exist like this where the general public has no idea it even exists, though they (most likely) use it every single day.
Re:Systems Correctness Practices at Amazon Web Services by ninetyninenine on Friday May 30, 2025 @02:59PM (#44138999)
I find red dead redemption 2 more impressive. I don’t know why. It sounds stupid but S3 on the surface has the simplest api and it’s just not impressive to me when compared to something like that.

I’m curious which one is actually more impressive in general.

Re:Systems Correctness Practices at Amazon Web Services by SteveNuts on Friday May 30, 2025 @04:25PM (#44139583)
Simple to use from an external interface yes, the backend is wildly impressive.

Some previous discussion https://news.ycombinator.com/item?id=36900147

Re:Systems Correctness Practices at Amazon Web Services by koito17 on Friday May 30, 2025 @09:28PM (#44141245)
> S3 on the surface has the simplest api and it’s just not impressive [...]

Reminded of the following comment from not too long ago.

https://news.ycombinator.com/item?id=43363055

Re:Systems Correctness Practices at Amazon Web Services by UltraSane on Friday May 30, 2025 @10:07PM (#44141392)
AWS has said that the largest S3 buckets are spread over 1 million hard drives. That is quite impressive.
Re:Systems Correctness Practices at Amazon Web Services by ninetyninenine on Friday May 30, 2025 @11:17PM (#44141645)
Red dead redemption 2 is likely on over 74 million hard drives.
Re:Systems Correctness Practices at Amazon Web Services by SteveNuts on Friday May 30, 2025 @11:56PM (#44141758)
There's likely over a trillion active SQLite databases in use right now.
Re:Systems Correctness Practices at Amazon Web Services by simonw on Saturday May 31, 2025 @09:23AM (#44144144)
I think you misunderstood. They're not saying S3 uses a million hard drives, they're saying that there exist some large single buckets that use a million hard drives just for that one bucket/customer!
Re:Systems Correctness Practices at Amazon Web Services by UltraSane on Monday June 02, 2025 @01:49PM (#44161322)
actually data from more than one customer would be stored on those million drives. But data from one customer is spread over 1 million drives to get the needed IOPs from spinning hard drives.
Re:Systems Correctness Practices at Amazon Web Services by sriram_malhar on Saturday May 31, 2025 @02:32AM (#44142294)
That's the strangest comparison I have seen. What axis are you really comparing here? Better graphics? Sound?
Re:Systems Correctness Practices at Amazon Web Services by ninetyninenine on Saturday May 31, 2025 @03:34AM (#44142629)
Complexity and sheer intelligence and capability required to build either.
Re:Systems Correctness Practices at Amazon Web Services by sriram_malhar on Saturday May 31, 2025 @05:51AM (#44143153)
And what is the basis for your claim? You are not impressed by AWS's complexity and intelligence and capability to build and manage 1-2 zettabytes of storage near flawlessly?
Re:Systems Correctness Practices at Amazon Web Services by ninetyninenine on Saturday May 31, 2025 @09:48AM (#44144267)
Im more impressed by red dead redemption 2 or baldurs gate 3.

There is no “basis” other my gut feeling. Unless you can get quantified metrics to compare that’s all we got. For example if you had lines of code for both, or average IQ. Both would lead towards the “basis” which neither you or I have.

Re:Systems Correctness Practices at Amazon Web Services by theflyinghorse on Friday May 30, 2025 @03:56PM (#44139422)
Maybe. But Google do have a reputation which makes selecting them for infrastructure a risky endeavor
Re:Systems Correctness Practices at Amazon Web Services by throitallaway on Friday May 30, 2025 @01:38PM (#44138367)
From my POV Amazon designs its services from a "trust nothing, prepare for the worst case" perspective. Eventual consistency included. Sometimes that's useful and most of the time it's a PITA.
Re:Systems Correctness Practices at Amazon Web Services by rossjudson on Friday May 30, 2025 @10:45PM (#44141516)
GCS's metadata layer was originally implemented with Megastore (the precursor to Spanner). That was seamlessly migrated to Spanner (in roughly small-to-large "region" order), as Spanner's scaling ability improved over the years. GCS was responsible for finding (and helping to knock out) quite a few scaling plateaus in Spanner.
Re:Systems Correctness Practices at Amazon Web Services by 0xbadcafebee on Monday June 02, 2025 @11:07AM (#44159615)
> GCS comes across as a much better thought-out and built product

I've worked with AWS and GCS for a while, and I have the opposite opinion. GCS is what you get if you let engineers dictate to customers how they are allowed to do work, and then give them shit interfaces, poor documentation, and more complexity than adds value.

There's "I engineered the ultimate engineery thing", and then there's "I made something people actually like using".

Re:Systems Correctness Practices at Amazon Web Services by riknos314 on Friday May 30, 2025 @07:32PM (#44140716)
I had the distinct pleasure of working on S3 (Lifecycle) during the timeframe that the index team was working on the rearchitecture that enabled the read-after-write consistency.

I can confidently say that as impressive as S3 is from the outside, it's at least that impressive internally, both in implementation, and organizational structure.

Re:Systems Correctness Practices at Amazon Web Services by up2isomorphism on Saturday May 31, 2025 @02:05AM (#44142187)
S3 is not a piece of software per se, it is a service.

Also S3 is not better than gcs or azure blob.

Re:Systems Correctness Practices at Amazon Web Services by simonw on Saturday May 31, 2025 @09:22AM (#44144134)
Services are built on software.

S3 is likely an order of magnitude larger then those others - it's had a lot longer to grow.