Synchronous executor interface

Attila Kelemen attila.kelemen85 at gmail.com
Sun Aug 6 20:44:52 UTC 2023


Robert Engels <rengels at ix.netcom.com> ezt írta (időpont: 2023. aug. 6., V,
22:35):

> You wouldn’t design it that way. The database driver would (or database)
> would control the concurrency - and it would be configured externally. Why
> would attempt to do this at the app level - the database is an external
> shared resource.
>

As soon as I pressed the send button, I realized that the DB is not a good
example, though not as you wrote, since it is not normally the
responsibility of the JDBC driver, but a connection pool which you
configure (still you have to do that at app level as well usually).

Anyway, that does not change the fact that there are a lot of cases where
you have to put a limit, and there is nothing readily available. Such as
sending a http request to a service, and you might want to limit the number
of concurrent access per service as well as the number of concurrent http
calls (across all services). Of course, there are countless other reasons
you might want to limit concurrent executions, and I see no reason not to
add a single interface that would be widely usable across different domains.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/loom-dev/attachments/20230806/ba6dcd12/attachment.htm>


More information about the loom-dev mailing list