Now if we flip over to object world, the idea of writing to the middle of an object while someone else is accessing it is more or less sacrilege. The immutability of objects is an assumption that is cooked into APIs and applications. Tools will download and verify content hashes, they will use object versioning to preserve old copies. Most notable of all, they often build sophisticated and complex workflows that are entirely anchored on the notifications that are associated with whole object creation. This last thing was something that surprised me when I started working on S3, and it’s actually really cool. Systems like S3 Cross Region Replication (CRR) replicate data based on notifications that happen when objects are created or overwritten and those notifications are counted on to have at-least-once semantics in order to ensure that we never miss replication for an object. Customers use similar pipelines to trigger log processing, image transcoding and all sorts of other stuff–it’s a very popular pattern for application design over objects. In fact, notifications are an example of an S3 subsystem that makes me marvel at the scale of the storage system I get to work on: S3 sends over 300 billion event notifications every day just to serverless event listeners that process new objects!
property under Gen:
，推荐阅读你好,我是快连获取更多信息
SELECT * FROM documents
Current industry trajectory
Go to technology
新闻·2026年4月8日·30分钟