Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I need to figure out between AWS SDK Java APIs and Jets3t APIs ? which is better in terms of throughput and performance?
I am assuming connection is not reliable so i may need to upload/download data in chunks.
There is API for multipart upload in JetS3t. But i am also looking for multipart download.
In my opinion, I would go with AWS SDK.
I did the switch 6 months ago and so far I have a good experience. I can’t answer you precisely in terms of throughput and performance but one thing that I can tell you is that it is less error prone. Sometimes, I experienced weird behaviours/bugs with Jets3t before switching to the AWS SDK.
One thing you should also consider is the support offered by both libraries. Jets3t are now rarely releasing new versions. Jets3t releases a new version about every 6 months or more, comparing to Amazon that releases a new version of their SDK about every 2 weeks.
So if Amazon changes something or fix something in their services you are likely to profit more of it be using the Amazon API instead of the Jets3t API.
If you would have asked the same question 2 or 3 years ago my answer would have been different but now in my opinion the SDK from Amazon is mature enough and offers better support/stability than Jets3t.