A lightweight, high-performance MVC web framework for Java 8 built on Netty, designed for simplicity and elegance.
Blade is a lightweight, high-performance MVC web framework for Java 8. It is built on Netty and designed to provide a simple, elegant alternative to heavier Java web frameworks, allowing developers to create efficient web applications and RESTful APIs with minimal configuration and overhead.
Java developers seeking a fast, modern, and uncomplicated web framework for building APIs and web applications, especially those who want to avoid the complexity of larger frameworks like Spring MVC.
Developers choose Blade for its exceptional performance, tiny footprint, and straightforward design. It offers a full-featured MVC experience without the bloat, making it ideal for microservices and projects where simplicity and speed are critical.
:rocket: Lightning fast and elegant mvc framework for Java8
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Built on Netty 4 with a source size under 500KB, Blade delivers over 100k queries per second, making it ideal for high-throughput applications as highlighted in the README.
Can be packaged as a standalone JAR and run without a servlet container, simplifying deployment and reducing overhead, with configuration options for port and SSL.
Leverages Java 8+ features like streams and lambdas to provide a fluent DSL for clean, concise code, as shown in the route registration examples.
Includes middleware for CSRF and XSS defense, plus Basic Auth, helping secure applications with minimal configuration, which is documented in the security features section.
Has fewer plugins, extensions, and community resources compared to mainstream frameworks like Spring, which can increase development time for complex features not covered in the README.
The default template engine is simplistic, and while pluggable engines like Jetbrick are supported, advanced templating requires additional setup and integration, as admitted in the README.
Lacks out-of-the-box support for ORM, distributed caching, or microservices patterns, necessitating custom implementations or reliance on external libraries.