[Feature] quarkus/helidon/micronaut support

[thegenius]

Pre-check

• I am sure that all the content I provide is in English.

Search before asking

• I had searched in the issues and found no similar feature requirement.

Apache Dubbo Component

Java SDK (apache/dubbo)

Descriptions

Now, many small companies and new projects are starting to use modern frameworks such as Quarkus, Helidon, and Micronaut.
（1）Among these, Quarkus is favored because its development experience is far superior than Spring, especially in terms of hot updates, and it supports GraalVM, which can save a significant amount of memory.
（2）Micronaut, with its compile-time dependency injection and AOP, has attracted many developers who dislike reflection.
（3）Helidon, by rewriting many Netty functionalities, offers excellent modularity and virtual thread support, also attracting a certain number of developers.
At the same time, there is an increasing willingness among developers to adopt Jakarta standardized annotations, as standardization typically means that code is not tied to a specific framework, reducing future migration costs.
Therefore, supporting these modern frameworks is a path that Dubbo 3 needs to take. I wonder if the development team has any related plans?

Related issues

No response

Are you willing to submit a pull request to fix on your own?

• Yes I am willing to submit a pull request on my own!

Code of Conduct

• I agree to follow this project's Code of Conduct

[oxsean]

Very valuable.
If you're interest on it, you can have a try.
Here's a brief overview to support Quarkus by ChatGPT:

1. Configuration Management

• Bind Dubbo configurations to Quarkus's configuration framework using @ConfigMapping.
• Dynamically load configurations into Dubbo at startup.

2. CDI Integration

• Enable Dubbo services as CDI beans for annotation-based service publishing and injection.
• Provide a mechanism for dynamic proxy creation for Dubbo references via CDI.

3. Hot Deployment Support

• Ensure Dubbo services can dynamically register and unregister during Quarkus's hot deployment (quarkus:dev).

4. Native Image Compatibility

• Ensure Dubbo's reflection and dynamic class loading work in GraalVM native images.
• Use @RegisterForReflection or a reflection configuration file for required classes.

5. Monitoring and Metrics

• Integrate with Quarkus's Micrometer framework to expose Dubbo metrics (e.g., QPS, latency) to Prometheus or other systems.

6. Security

• Utilize Quarkus's security framework (e.g., OAuth2, JWT) for unified authentication and authorization of Dubbo service calls.
• Add global interceptors for token validation and security context propagation.

7. Quarkus Dev UI

• Provide a Dev UI extension to visualize Dubbo service registrations, metrics, and call statistics during development.

By implementing these integrations, Dubbo can seamlessly adopt Quarkus's developer-friendly features, ensuring high performance, easy configuration, and enhanced compatibility for modern Java applications.