sirix icon indicating copy to clipboard operation
sirix copied to clipboard

Using Quarkus(.io) for the REST-API bundle/module.

Open JohannesLichtenberger opened this issue 4 years ago • 6 comments

This would give us a better starting point for getting a Kubernetes cluster up and running in the future. Maybe also using the GraalVM with native binaries. As we didn't use reflection and other stuff which would prohibit the use of native binaries the only thing now is that we moved to Java 13 and the GraalVM just started to support Java 11.

JohannesLichtenberger avatar Dec 25 '19 17:12 JohannesLichtenberger

Did you mean https://quarkus.io/ ? (Note: quarkus instead of quarkis) I'm not familiar with that project but I didn't find anything under quarkis.io and it seems like the right thing.

zacharywhitley avatar Jan 06 '20 18:01 zacharywhitley

Yes, Quarkus, sorry...

JohannesLichtenberger avatar Jan 06 '20 18:01 JohannesLichtenberger

No worries, I just wanted to make sure I was looking at the right thing :) I've had my eye on Sirix for a little while and wanted to dig in a little more.

zacharywhitley avatar Jan 06 '20 18:01 zacharywhitley

Very cool. Let me know if I can help. And if you use SirixDB and encounter bugs, please let me know :-)

JohannesLichtenberger avatar Jan 06 '20 18:01 JohannesLichtenberger

For reference:

Vert.x quickstart: https://github.com/quarkusio/quarkus-quickstarts/tree/master/vertx-quickstart

And the Router based approach using the Vert.x ALI directly instead of all this Annotation based stuff:

https://quarkus.io/guides/reactive-routes#using-the-vert-x-web-router

JohannesLichtenberger avatar Jan 06 '20 19:01 JohannesLichtenberger

Not sure we need Quarkus. I think Vert.x underlying Quarkus is perfectly ok. I think peak performance might be necessary as well (via JIT compilation), in comparison to fast startup times and low memory footprint (with AOT compilation).

JohannesLichtenberger avatar Feb 25 '23 17:02 JohannesLichtenberger