OSS TanbouSign in with GitHub

Build lean JVM applications by preparing dependency injection and HTTP infrastructure at compile time

About these scores

OSS scale score is an unbounded metric that log-compresses and weights Stars, Watchers, Forks, and Contributors. Discovery score is the current OSS scale score minus the score at discovery. Update pace is commits in the last 30 days, growth momentum is the OSS scale score difference within the recent observation window, and OSS health is a 0–100 rating based on available recency, Community Health, and release data.

Stars
6,430
Primary language
Java
License
Apache-2.0
Repository last updated
Oct 4, 2026
On this page

Overview

Micronaut Framework is a full-stack framework for modular JVM applications written in Java, Kotlin, or Groovy. It prepares dependency injection, AOP, and auto-configuration infrastructure at compile time, reducing runtime reflection and proxy generation. HTTP servers, command-line programs, message-driven applications, and microservices with discovery or client-side load balancing can share the same foundation.

Features and best fit

Based on official documentation; not hands-on tested · Content checked:

Key features

Prepare dependency injection and AOP at compile time

Annotation processing precomputes framework infrastructure and reduces reliance on runtime reflection, dynamic proxies, and bytecode generation. HTTP services and serverless functions can retain JVM types and tooling while reducing work at startup and during execution.

Sources: [2]

Use one foundation for HTTP, messaging, and distributed services

The framework includes HTTP routing, client-side load balancing, distributed configuration, and service discovery, and it also supports command-line and message-driven applications. Java, Kotlin, and Groovy support lets teams reuse JVM assets and existing language experience.

Sources: [2]

Best fit

Fits JVM services where startup time and memory use matter

It suits containerized or serverless systems with many small services, teams building typed HTTP APIs on the JVM, and applications that need testable module boundaries. It is also a candidate for teams bringing Spring-family experience to a framework designed to reduce runtime work.

Sources: [2]

Before adoption

Account for compile-time processing and extension compatibility

Because more behavior is fixed at compile time, libraries that dynamically assemble types or configuration may require Micronaut-specific integration. APIs marked @Experimental or @Internal are excluded from the project’s Semantic Versioning public-API commitment. Review compatible versions and native-image requirements for every data, cloud, and messaging module used alongside Core.

Sources: [2][3][4]

Official sources

  1. [1]micronaut-projects/micronaut-core repository metadata(2026-10-04)
  2. [2]Micronaut Core v5.2.13 README(2026-10-04)
  3. [3]Micronaut Core v5.2.13 release(2026-10-04)
  4. [4]Micronaut Core v5.2.13 Gradle properties(2026-10-04)
  5. [5]Micronaut Core v5.2.13 Apache-2.0 license(2026-10-04)
Supplemental curator note

Compare JVM frameworks with the actual data and cloud modules included, measuring build time and operating memory instead of relying on startup benchmarks alone. Identify libraries that do not fit compile-time processing early.

Try it in 3 steps

  1. 1

    Clone the reviewed source tag

    Shallow-clone v5.2.13 and enter the Core working tree. Its pinned Gradle 9.7.1 wrapper needs a JDK from 17 through 26, Git, and network access for dependencies.

    git clone --depth 1 --branch v5.2.13 https://github.com/micronaut-projects/micronaut-core.git && cd micronaut-core
  2. 2

    Publish Core to the local repository

    From the same working directory, use the Gradle Wrapper to build Core and publish it to the local Maven repository. This is a source build of the framework itself, not an end-user sample application.

    ./gradlew publishToMavenLocal
  3. 3

    Generate the reference documentation

    From the same working directory, generate the Core reference documentation and inspect the completed output at build/docs/index.html. Allow time and disk space for dependency downloads and the documentation build.

    ./gradlew docs
Check the official README

Growth

Growth trends · Last 30 days

6,430 Stars

Trend data is still being collected.

Development activity

Last 90 days · weekly

Commits (last 30 days)
476
Open PRs
257

Development activity is still being collected.

Built with

Categories and tags

GitHub data

GitHub dataView detailed GitHub data

GitHub Topics

  • microservices
  • java
  • kotlin
  • groovy
  • cloudnative
  • serverless
  • python
  • python3
Stars
6,430
Forks
1,222
Watchers
165
Open issues
433
Contributors
499
Owner type
Organization
Primary language
Java
License
Apache-2.0
Repository last updated
Oct 4, 2026
Write a related article

Share a guide or use case for this OSS in Markdown. Articles are published after administrator approval.

Report incorrect information

Tell us if any listing information is incorrect or outdated.

After reading this page, do you know what to do next?