Repository navigation
SPI RESTful integration #39163
Unanswered
rentius2407
asked this question in
Q&A
SPI RESTful integration
#39163
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hello,
I’m considering integrating an SPI that communicates with another service via REST for user lookup and validation. This is specifically for the new Keycloak server (26.2), which runs on Quarkus.
However, initial testing indicates that the SPI is blocking on REST I/O and is spawning new executor threads, which seems in direct conflict with Quarkus's non-blocking, reactive nature. The server is running in Kubernetes and is struggling under load (load testing).
Would this approach be advisable, or is there a more Quarkus-aligned method using the SPI to handle such interactions without blocking?
All reactions