At this stage, the library doesn't use go routine, which is "fine" - as it can be implemented on the client side fairly easily when gathering lots of data. However when using multiple regions, this time cannot be save elsewhere than within the library.
Which is why, implementing go routine, for every call, could be a good idea in order to speed up the gathering of data from AWS - and let the client do it some more if need be.
At this stage, the library doesn't use go routine, which is "fine" - as it can be implemented on the client side fairly easily when gathering lots of data. However when using multiple regions, this time cannot be save elsewhere than within the library.
Which is why, implementing go routine, for every call, could be a good idea in order to speed up the gathering of data from AWS - and let the client do it some more if need be.