Support asynchronous clients about amazonica HOT 2 CLOSED

So basically it's a matter of efficient utilization of the thread pool. Each Amazon *AsyncCilent (for each different service in the api, e.g. SNS, RDS, EC2, etc.) is going to maintain it's own unbounded thread pool. Likewise, Clojure maintains it's own unbounded thread pool as well, for IO-bound tasks, used for future and send-off calls. The more I think about it, I would guess that any marginally complex application, which might see usage of future and send-off calls in other areas of the application, is going to have a higher probability of reusing a thread from Clojure's unbounded pool before it's 60s TTL has expired and its eviction from the pool. I would guess that the AWS service-specific pool would see less reuse of existing threads from its pool.

from amazonica.

What would be the benefit of using the AWS Async api rather than Clojure's built-in async facilities, so to use your example, something like:

(future
  (publish
    cred
    :topic-arn "arn:aws:sns:us-east-1:676820690883:my-topic"
    :subject "test"
    :message (str "Todays is " (java.util.Date.))))

AWS SDK and Clojure would both ultimately run the publish call on a separate thread obtained via Executors.newCachedThreadPool().

from amazonica.