lets-blade/blade
Blade
Blade is a lightweight Java MVC web framework built on an embedded Netty server. It packages the entire web application into a single executable JAR that starts the server on launch, following the MVC pattern with fast request routing and minimal configuration. The framework supports plugin-based extensibility, allowing third-party modules to add features like template rendering and static asset serving.
The framework distinguishes itself through lambda-style route registration, where routes are defined using lambda expressions that map HTTP methods and URL patterns directly to handler functions at startup. It includes a middleware pipeline architecture that executes pre-request hooks in a chain before route handlers, enabling cross-cutting concerns like logging and validation. Typed parameter extraction automatically converts path and query parameters from URLs into typed Java objects, while the plugin system loads third-party modules at runtime to extend core functionality without modifying the framework source code.
Blade handles RESTful route definition, file uploads, query parameter parsing, and JSON response serialization. It serves static assets from WebJars bundled inside the application JAR without extra configuration and renders dynamic HTML by integrating with external template engines. The framework is packaged as a standalone executable JAR that runs the embedded Netty server on launch.
Features
- Lightweight Java Implementations - Provides a lightweight Java MVC framework with embedded Netty server and minimal configuration.
- Netty-Based Servers - Runs an embedded Netty HTTP server inside the application JAR, handling all I/O without an external container.
- Executable JAR Packagings - Packages the entire web application into a single executable JAR that starts the embedded server on launch.
- Java Web - Provides a lightweight Java MVC framework for building web applications with fast request routing and minimal configuration.
- Plugin-Based Extensibility - Supports third-party plugins to extend core functionality like template rendering and static asset serving.
- Middleware Architectures - Executes pre-request hooks in a chain before the route handler for cross-cutting concerns like logging.
- Lambda-Based Route Definitions - Maps HTTP methods and URL patterns to handler functions using lambda expressions for REST API building.
- Functional Route Handlers - Maps HTTP methods and URL patterns to handler functions using lambda expressions at startup.
- Pre-Request Logic Hooks - Executes callback functions before every matching request for setup, logging, or validation tasks.
- Third-Party Plugins - Loads third-party modules to add new functionality without modifying the core application code.
- Request Middleware - Executes hook functions on every matching request before the route handler runs for cross-cutting concerns.
- Dynamic Template Rendering - Generates HTML views by integrating with template engines, separating presentation logic from application code.
- HTML Templating Engines - Renders dynamic HTML by plugging into external template engines, separating view logic from controllers.
- Web Frameworks - Lightweight and modular web framework.
