This is an old revision of the document!
A Microsoft Windows desktop application for object storage.
Object storage services are an essential part of many software developers daily lives. A software developer stores many things with an object storage service including packaged software builds, content for applications, operating system images and backups. Most of these activities are eventually automated, but during development and debugging developers need a tool to examine the state of their object storage environment.
These services have 1st-party consumer-oriented products which interface transparently with their object storage back-ends. Amazon Cloud Drive, Google Drive and Microsoft OneDrive are all intended to intertwine your personal data and daily routine with their data storage and complementary services.
Each service has a strong focus on fully featured APIs. This focus lends itself well to not just 3rd-party integration but entire 3rd-party interface replacements. This behavior by 3rd-party developers is strongly encouraged and openly supported by each service.
The goal is to become an essential Windows desktop application for managing an object storage environment.
Amazon's storage service is the most established service. It has the most resident mindshare among developers. It also has the largest number of 3rd-party desktop applications with fully developed feature sets and established audiences. This makes it inherently more expensive to enter the market as an S3 client.
Google's storage service is the most sophisticated implementation, allowing for consistent worldwide GET requests after a successful PUT. With their Spanner and Borg papers, they continue to push the boundaries on what is possible with planet-scale computing. It also has the most generic name of any service and search results pages about it are littered with Google self-promotion making market entry difficult for 3rd-party applications.
Microsoft's storage service is the most well-supported for a Microsoft Windows desktop application. The SDK and the programming language itself are 1st-party. It is also arguably the least-used storage service of the three. However, ease of market entry and initial customer acquisition combined with its 1st-party platform status makes the service my choice for a minimal implementation.