[Java/muserver] Add muserver #9902
Conversation
|
Please @gyakkun can you reference the work made at https://github.com/franz1981/Netty-VirtualThread-Scheduler or in #9800 🙏? I suggest to look at micronaut-projects/micronaut-core#11704 if you are using the loom event loop as a carrier with ORM or jdbc |
Thank you for your advice. Have done some other stress tests and observed other issue. Let me remove those loom and io_uring experiments and keep this PR simple first. Never too late to make things more complicated. |
| @Path("/json") | ||
| @Produces(APPLICATION_JSON) | ||
| public Map<String, String> json() { | ||
| return helloWorld; |
There was a problem hiding this comment.
Unless you're recreating the TFBResource on every request, this violates the JSON test rules.
There was a problem hiding this comment.
Sure. Fixed accordingly.
| @Path("/plaintext") | ||
| @Produces(TEXT_PLAIN) | ||
| public String plaintext() { | ||
| return "Hello, World!"; |
There was a problem hiding this comment.
I'm going to merge this one, but technically our PLAINTEXT test rules mean that you could literally make this a statically allocated byte array and simply use it here instead of returning a new instance every call.
* [Java/muserver] Add muserver. * Create object on request to adhere TFB rules.
3 participants
muserver is a netty-based, jax-rs compatible http server implementation in Java.
The test is written in common pattern of muserver, including a jax-rs resource class handler implementation (the default one) and a library built-in
MuHandlerimplementation (reduces reflection and should be faster).Scaffolding scripts and dockerfiles are modified from netty.
The database connection and ORM part is modified from Javalin tests.
Verified on local machine: