Public, candid feedback is generally about Quarkus rather than necessarily IEBQ specifically. The community signals provide context for likely adoption risks and benefits.
Positive / neutral themes
- Performance characteristics such as reduced startup time and smaller memory footprint are frequently cited, and tooling (CLI, dev mode) receives favorable mentions.
- Example (general adoption consideration): In a Reddit discussion, a commenter described Quarkus performing initialization at compile time, which reduces runtime footprint and startup duration, and mentioned the CLI and tooling as helpful.
Negative / skeptical themes
- Ecosystem gravity: multiple threads note that most enterprise software uses Spring Boot, implying library familiarity and hiring patterns can be a barrier.
- Governance and ownership perceptions: some community posts conflate vendor involvement and project governance; buyers should validate foundation and governance arrangements separately.
- Native build friction: users frequently report native-image build challenges with certain libraries (for example, additional build arguments and debugging required for some cloud libraries), which is a recurring theme in Quarkus communities.