Split up into smaller modules

[twilek]

Is there any plans to split this project up into smaller modules? One module per service would be sensible, and then a few modules with code that it is share between them. Now you have to import almost 15 megabyte of dependencies if you just want to do the smallest thing. Not very modular and makes deploys much slower.

For those who sill just want the whole package you can still keep the original aws-java-sdk module that just gather all the smaller modules. In this way you can also do such a split up but still be backward compatible.

Since the project already have the cohesion where every service already has its own package such a split up would probably not be very hard to do. The only problem I see is the util package that that suffer from coincidental cohesion and would maybe need some breaking changes if not all modules shall not need to depend on all that this package relates to.

[fulghum]

Hey Martin, thanks for the feedback. This is something we've considered for a while, and as the number of AWS services grows, it makes more sense. We listen closely to customer feedback to prioritize development, so this is very helpful.

[tomparle]

Hi, I second Martin on this one. More than 15MB of deps slows down my deployement and thus development time, and I would really appreciate a split of the SDK.
Tom

[tomassommar]

Hello, I agree with Martin as well. This would be very appreciated.

[dej]

Hello, this is also something that we would like to see.

[asieira]

+1

[bvirlet]

+1

[guillaume-tgl]

+1

[rmuhamedgaliev]

+1

[usultis]

+1

[udgupta]

+1

[sedan07]

+1

[manikandanrs]

Thanks for opening this issue. The latest release of AWS Java SDK (1.9.0) now has been split into multiple modules. For more information, check out the release notes https://aws.amazon.com/releasenotes/7291607733354976