This document discusses Amazon S3, including CAP theory, eventual consistency vs read-after-write consistency, regions, security, comparisons between S3 and S3N, limitations of S3, use of S3 with Hadoop, and S3 performance. It explains that S3 provides eventual consistency by default but some regions support read-after-write consistency. It also notes limitations on file names for S3 buckets and the 5GB file size limit of S3N for Hadoop.
5. Read after Write consistent
Amazon S3 壓仟秀Y創r頁λ嗤c恬匯
崑來秘。
Less latency : 侭嗤Client 壓心欺仟秀Y創頁恷仟
議
6. 恷K匯崑來式匯崑來曳^
Eventually Consistent Read Consistent Read
Stale reads possible No stale reads
Lowest read latency Potential higher read latency
Highest read throughput Potential lower read throughput
7. Region
Region Puts (new object) OverWrite
Puts,Delete
US Standard eventual consistency eventual consistency
US West (Oregon)
Region
read-after-write
consistency
eventual consistency
US West (Northern
California) Region
read-after-write
consistency
eventual consistency
EU (Ireland) Region read-after-write
consistency
eventual consistency
Asia Pacific
(Singapore,Tokyo,Syn
de) Region
read-after-write
consistency
eventual consistency
? South America (Sao
Paulo) Region
read-after-write
consistency
eventual consistency
12. S3 Performance
Request Rate and Performance
S3 bucket routinely exceeds 100
PUT/LIST/DELETE requests per second
more than 300 GET requests per second
TCP Window scaling
Amazon S3 by supporting window sizes larger
than 64 KB