Framework Compatibility Enhancement Proposal

[anandjaisy]

Overview
Embabel is an excellent framework; however, it is currently tightly coupled with the Spring ecosystem. With the evolution of modern development practices, frameworks such as Micronaut and Quarkus have emerged, offering faster startup times, lower memory footprints, and improved cloud-native support.

Problem Statement
Because Embabel is dependent on Spring, it is challenging to integrate or adopt it within other modern frameworks. This limits its usability and reach among developers who are leveraging lightweight, high-performance alternatives to Spring.

Proposed Enhancement
It would be highly beneficial to make Embabel framework-agnostic or to provide integration support for Micronaut and Quarkus. This would enable broader adoption, improve flexibility, and position Embabel as a more versatile solution in the evolving Java ecosystem.

[johnsonr]

I'm talking in detail to some Quarkus engineers about decoupling. Reducing coupling would be sound engineering practice.

We're happy to support such efforts and unpick where it makes sense. It's a question of priority. Spring remains dominant on the JVM, and is likely to continue to, so it's unlikely we'd gain a huge number of users through decoupling.

[sschellh]

It would be great to use Embabel within a JakartaEE or Quarkus based application! I like the proposed idea to make Embabel framework agnostic.