carbon
This library vs AWS SDK for .NET
Hello
I'm a dev on the official AWS SDK for .NET and I was curious what were your design goals that you had to warrant writing your own versus using ours. Where there things lacking in our SDK that you wanted to improve on?
Impressive work writing your own SDK.
Norm
Can I just add this this is published in nuget with the package name Amazon.S3 which can be confusing to people that are looking for the office SDK. I would use another namespace (Carbon.S3) to avoid confusion.
An alternative SDK becomes necessary when you run into blocking issues in the official AWS SDK. For example, there is a threading issue which is causing an occasional lock in AWS SDK for DynamoDb:
https://github.com/aws/aws-sdk-net/issues/1476
I've resorted to writing my own API wrapper to circumvent this until I found this SDK.
In Nuget, this package is way too similar to the official AWS package. For inexperienced devs or those just not paying attention, this package will get installed instead of the official AWS package.
As I was about to install this package, I realized that the Nuget information was missing the project URL; the only way I found this project was by going to the Nuget website and finding the source repository.
At a minimum, this package should be renamed to something like: Amazon S3 Wrapper. And update the description so it clearly states this is not the official AWS S3 package, but an alternative. Finally, the Readme for this repo really should clearly state this is not the official AWS package, and then provide concrete examples of why this wrapper is needed.
Nearly 500k downloads; I'm gonna go out on a limb and say the vast majority thought they were downloading the official AWS package.
