Author: admin
-
Reference Guides
A collection of useful official reference guides that serves as bookmarks. Core Contexts and Dependency InjectionCross-Origin Resource Sharing (CORS)HTTP ReferenceLogging configurationMailer Reference GuideVert.x Reference Guide gRPC gRPC reference guidegRPC code generation reference guide
-
Configuration Reference
This article is a collection of configuration references. Quarkus Configuration See source for more: https://quarkus.io/guides/config-reference Datasource Configuration See source for more: https://quarkus.io/guides/datasource
-
Getting Started
This article summarizes content from the Quarkus Getting Started Guide Differences from vanilla Jakarta REST With Quarkus, there is no need to create an Application class. It’s supported, but not required. In addition, only one instance of a REST resource is created and not one per request. You can configure this using the different *Scoped annotations (ApplicationScoped, RequestScoped, etc).
-
Class Loading Reference
The Quarkus class loading architecture is slightly different depending on the mode that the application is run in. When running a production application using the fast-jar package type (which is the default), almost all dependencies are loaded via the io.quarkus.bootstrap.runner.RunnerClassLoader which indexes classes at build time, while a small set of dependencies is loaded from the system ClassLoader. When
-
Getting Started with Reactive
Source: https://quarkus.io/guides/getting-started-reactive Quarkus is a Reactive framework. Since the beginning, Reactive has been an essential tenet of the Quarkus architecture. It includes many reactive features and offers a broad ecosystem. This guide is not an in-depth article about what Reactive is and how Quarkus enables reactive architectures. If you want to read more about these topics, refer to the Reactive Architecture guide, which provides