jsr339-experts@jax-rs-spec.java.net

[jsr339-experts] Re: [jax-rs-spec users] Async API Usage Guidance

From: Marek Potociar <marek.potociar_at_oracle.com>
Date: Mon, 1 Oct 2012 13:27:25 -0700

On Sep 30, 2012, at 1:30 PM, Jan Algermissen <jan.algermissen_at_nordsc.com> wrote:

> All,
>
> based on the implementation experience with the Async API to date, can you provide advice on what a developer should consider a 'long running operation'?
>
> What operations are usually long running enough to see a server performance or capacity gain when switching to the async API?

I guess it also depends on your container I/O thread-pool setup, and the expected request rate. In general, anything that involves another I/O operation (file, DB, network) is a good candidate for switching to async API. But it's just a rule of thumb...

HTH,
Marek

>
> File IO?
> JPA data read?
> JPA data write?
> Upstream HTTP request?
> ...
>
>
> Jan