lets-blade/blade

:rocket: Lightning fast and elegant mvc framework for Java8

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 57 minutes ago
Added to GitGenius on September 11th, 2026
Created on June 10th, 2015
Open Issues & Pull Requests: 14 (+0)
GitHub issues: Enabled
Number of forks: 1,151
Total Stargazers: 5,872 (+0)
Total Subscribers: 279 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

Blade is a lightweight MVC framework for Java that builds on Java8 and Netty4 to deliver high-performance web applications with minimal dependencies.

The framework addresses the complexity and overhead of traditional Java web stacks by providing a streamlined alternative that eliminates unnecessary layers. It uses a RESTful-style routing design with a streams-style API, allowing developers to write web services with direct access to core functionality rather than navigating through abstraction layers. The codebase is kept small, under 500kb, making it straightforward to understand and learn. Blade includes built-in features such as a template engine, CSRF and XSS defense, Basic Auth and Authorization, plugin extension support, cron-based task scheduling, and commonly used middleware.

Blade suits developers who want to build web applications quickly without the complexity of frameworks like Spring or traditional SSH stacks. It works well for projects where simplicity and performance matter more than an extensive ecosystem of third-party integrations. The framework is designed to be learned in a single day and can be deployed as a standalone JAR file, making it practical for microservices and small to medium-sized applications. The README positions it as an alternative to heavier frameworks, emphasizing that it removes bloat while maintaining flexibility through its modular design and plugin system.

The project maintains active engagement through community channels and accepts contributions. Development follows standard practices with continuous integration and code quality monitoring in place.