Migrating High-Throughput Redirector Service to Quarkus + JDK 25: Virtual Threads & Pinning Concerns #55459
KarthiSM
started this conversation in
Design Discussions
Replies: 2 comments
-
|
I would not switch to Quarkus 3.8, it's very old. Use 3.33.x (latest LTS). |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I'm in very high event - driven service (based akka, sbb, jainslee design). if you looking into 10 mil tps (1 - 100 Gbps) then take a look https://github.com/nhanth87/jain-slee |
Beta Was this translation helpful? Give feedback.
0 replies
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.
-
Context:
Modernizing a critical traffic routing service (millions of requests/day) from Spring 5.3.20 + Jetty 9.4.58 + Java 8 to Quarkus + JDK 25 for virtual thread benefits.
Current Architecture:
Key Questions:
Saw the GitHub discussion (JDK 25 Support? When? #50130) mentioning "problematic pinning when loading classes" with virtual threads.
Our biggest blocker: Custom Spring scopes for per-application bean lifecycle.
@component
@scope(AppScope.APP_SCOPE) // No Quarkus equivalent?
public class ApplicationRulesCache { }
Which sequence is recommended?
Our Plan:
Does this make sense?
Looking for: Real-world Spring→Quarkus migration experiences, JDK 25 stability insights, custom scope patterns, virtual thread pinning war stories.
Tags: #quarkus #jdk25 #virtual-threads #spring-migration #production
Beta Was this translation helpful? Give feedback.
All reactions