What we really desired was the ability to expose a meta-store, transparently backed by different cloud providers’ storage offerings. Looking at the bigger picture, S3 was simply an expensive default choice among many competitors-including our own M agic P ocket block store. Caches built against S3 burned pricey GET requests with each cache miss.
For instance, crash traces wrote many objects which were rarely accessed unless specifically needed for an investigation, generating a large PUT bill. Using these two legacy systems as generic blob storage caused many pain points-the worst of which was the cost inefficiency of using S3’s API. Among these use cases were crash traces, build artifacts, test logs, and image caching. Although we migrated user file data to our internal block storage system Magic Pocket in 2015, Dropbox continued to use S3 and HDFS as a general-purpose store for other internal products and tools. Dropbox originally used Amazon S3 and the Hadoop Distributed File System (HDFS) as the backbone of its data storage infrastructure.
0 kommentar(er)
