networknt/light-4j

A fast, lightweight and more productive microservices framework

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 26 minutes ago
Added to GitGenius on September 18th, 2026
Created on September 9th, 2016
Open Issues & Pull Requests: 15 (+0)
GitHub issues: Enabled
Number of forks: 625
Total Stargazers: 3,672 (+0)
Total Subscribers: 181 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.0 hours
Mean response time: 28.3 days
90th percentile: 20.0 hours
Tracked items: 314

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Practically every issue opened in the past year has drawn a reply. 98% of issues opened in the past year have since been closed. Three people close 100% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 4
New in 7 days: 7
Closed in 7 days: 5
Avg open age: 106 days
Stale 30+ days: 1
Stale 90+ days: 1

Recent activity

Opened in 7 days: 7
Closed in 7 days: 5
Comments in 7 days: 1
Events in 7 days: 4

Top labels

  • enhancement (11)
  • bug (9)
  • wontfix (1)

Detailed Description

Light-4j is a fast, lightweight, and cloud-native microservices framework for Java.

The framework addresses the performance and productivity limitations of Java EE and Spring Boot by providing a platform designed specifically for microservices deployed in containerized cloud environments. It is built on the Undertow HTTP core and emphasizes a clean separation between business logic and technical cross-cutting concerns. The approach prioritizes a small memory footprint, high throughput, and low latency as fundamental design goals rather than afterthoughts.

Light-4j suits teams building microservices that need to minimize resource consumption and operational costs. It is particularly valuable for organizations deploying many containerized services where memory usage and startup time directly impact infrastructure expenses. The framework is designed for cloud-native deployment from the ground up, making it well-suited to container orchestration environments. Developers should choose it if they have rejected Spring Boot and Java EE as too resource-heavy for their use cases and want a platform that treats performance as a core architectural principle.

The project maintains active community engagement through multiple channels including Stack Overflow, a Google Group, Gitter chat, a subreddit, and a YouTube channel. Development is driven by sustained commitment to the framework's core principles and ecosystem expansion, with the maintainer actively soliciting sponsorship to dedicate full effort to the platform. The project continues to evolve with production deployments across multiple companies providing feedback that informs ongoing development.