Helidon
Oracle's lightweight Java microservice framework — supports two styles: Helidon MP (MicroProfile compliant, CDI injection, JAX-RS REST) and Helidon SE (functional reactive style, no IoC container). Helidon 4.x uses Java 21 Virtual Threads (Project Loom) for high concurrency without reactive programming complexity. Key features: GraalVM native image support (fast startup, low memory), built-in health checks (MicroProfile Health), metrics (MicroProfile Metrics), tracing (Jaeger/Zipkin), security (JWT, OAuth2, OIDC), and OpenAPI (MicroProfile OpenAPI). Oracle's alternative to Quarkus and Micronaut.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
MicroProfile JWT for token-based auth. OIDC integration for enterprise SSO. TLS via Helidon server config. Oracle Cloud IAM integration for OCI deployments. MicroProfile security APIs are well-defined standards.
⚡ Reliability
Best When
You're deploying Java microservices on Oracle Cloud Infrastructure, need MicroProfile compliance, or want GraalVM native image support with fast startup for agent containers without Quarkus.
Avoid When
You need Spring ecosystem integration, your team is Spring Boot-experienced (migration cost), or you're not deploying to Oracle Cloud (Quarkus and Micronaut are more widely supported elsewhere).
Use Cases
- • Build lightweight Java agent microservices with fast startup using Helidon + GraalVM native image — agents start in <50ms for serverless/container deployments
- • Create MicroProfile-compliant agent APIs using Helidon MP — JAX-RS annotations, CDI injection, and MicroProfile extensions with minimal Helidon-specific API
- • Implement high-concurrency agent services using Helidon SE + Virtual Threads — blocking code with high concurrency without reactive complexity via Project Loom
- • Add health checks and metrics to agent services using MicroProfile Health and Metrics — /health and /metrics endpoints auto-configured with Helidon MP
- • Build agent services with Oracle Cloud/OCI integration — Helidon has native OCI SDK support for Oracle Cloud agent deployments
Not For
- • Teams deeply invested in Spring ecosystem — Helidon doesn't integrate with Spring ecosystem; Spring Boot is the industry standard with far broader library support
- • Non-Oracle cloud deployments where Quarkus or Micronaut are better supported — Helidon is optimized for Oracle Cloud; Quarkus and Micronaut have broader cloud-native community
- • Developers expecting Spring Boot-like auto-configuration breadth — Helidon's ecosystem is smaller; fewer pre-built integrations for third-party services vs Spring Boot
Interface
Authentication
Helidon MP provides MicroProfile JWT authentication (@RolesAllowed, @Authenticated), OIDC integration (Keycloak, Auth0), and OAuth2 client credentials. helidon-security-providers for comprehensive auth configuration.
Pricing
Helidon is Apache 2.0 licensed, maintained by Oracle. Free for all use.
Agent Metadata
Known Gotchas
- ⚠ Helidon MP vs SE are architecturally different — Helidon MP uses CDI + JAX-RS (like Quarkus); Helidon SE is programmatic with no IoC; mixing documentation from both flavors in implementation causes confusion
- ⚠ GraalVM native image requires reflection registration — classes accessed via reflection (JSON, CDI proxies) must be registered in reflection.json; missing registration causes NoSuchMethodException in native image but works in JVM mode
- ⚠ Virtual threads (Helidon 4.x) require Java 21+ — Helidon 4.x uses Project Loom virtual threads; Java 17/11 requires Helidon 3.x with different API; ensure JDK version compatibility
- ⚠ MicroProfile Config injection timing — @ConfigProperty values injected at CDI bean creation time; dynamic config changes after startup don't refresh injected values without explicit Config.getValue() programmatic access
- ⚠ Helidon MP OIDC security requires full configuration — helidon.security.providers[0].oidc.* properties must include discovery-uri, client-id, client-secret; partial config causes silent auth failure returning 401 without explanation
- ⚠ Helidon 3.x vs 4.x migration — Helidon 4 changed from reactive Netty to Virtual Threads + NIO; API classes moved packages; existing Helidon 3 reactive code requires refactoring; check migration guide before upgrading
Alternatives
Full Evaluation Report
Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Helidon.
Scores are editorial opinions as of 2026-03-06.