5 ms·
AWS fixed S3 consistency in December 2020: https://aws.amazon.com/about-aws/whats-new/2020/12/amazon-s3-now-delivers-strong-read-after-write-consistency-automa
by wolf550e 5y ago
AWS fixed S3 consistency in December 2020:
https://aws.amazon.com/about-aws/whats-new/2020/12/amazon-s3-now-delivers-strong-read-after-write-consistency-automatically-for-all-applications/ https://aws.amazon.com/about-aws/whats-new/2020/12/amazon-s3...
- swyx 5y agothats... what the post is about..
- deepsun 5y agoBy the way, Google's GCS had it from the beginning.
- BrandonY 5y agoHi, GCS engineer here. GCS offered a lot of consistency from the beginning, but we didn't have strong object listing consistency at the beginning. We got that somewhere around 2017 when we moved object metadata to Spanner. See https://cloud.google.com/blog/products/gcp/how-google-cloud-storage-offers-strongly-consistent-object-listing-thanks-to-spanner https://cloud.google.com/blog/products/gcp/how-google-cloud-...
- CommanderHux 5y agoAzure had it from the beginning
- kondro 5y agoAzure doesn't let you write more than 20MB/s to an storage account.
- jiggawatts 5y agoWhat are you talking about? The default ingress rate is 10 Gbps: https://docs.microsoft.com/en-us/azure/storage/common/scalability-targets-standard-account#scale-targets-for-standard-storage-accounts https://docs.microsoft.com/en-us/azure/storage/common/scalab... Elsewhere they state maximum scalability targets of 400 Gbps egress and 80 Gbps ingress: https://docs.microsoft.com/en-us/azure/storage/files/storage-files-scale-targets#storage-account-scale-targets https://docs.microsoft.com/en-us/azure/storage/files/storage...