Guided Learning Path
Follow sections in order. Each page prepares the next, ensuring no environment or deployment prerequisites are missed.
NioFlow Documentation
Professional Framework Guide
Start from installation and move step-by-step to routing, authentication, frontend integration, deployment, and production hardening.
What You Will Build
This guide is focused on practical delivery. By the end, you will have a real Java backend using NioFlow routes, structured middleware, JWT-protected APIs, health and readiness probes, and a cloud-ready runtime setup that can be deployed to Docker, Render, or Railway.
Every section includes copy-paste examples and production defaults so you can move from local proof-of-concept to release candidate without rewriting the architecture.
1. Getting Started
Download options, Maven vs manual setup, project bootstrap, and port registration strategy.
2. Routing + Frontend
Build custom routes, parse request body/path params, and integrate with frontend fetch clients.
3. Auth + Security
Implement signup/login, generate JWT tokens, protect route groups, and set security baselines.
4. Database + Env
Orchestrate secrets with .env files, connect to Supabase/Postgres, and manage connection pools.
5. Operations + Deployment
Operational readiness, deploy strategy, probes, incident basics, and release delivery workflow.
6. Reference
Configuration matrix, endpoint reference, starter zip endpoint design, and troubleshooting.
7. Performance
Load test results, throughput analysis, latency matrix, and hardware validation reports.
Production-Readiness
Examples are complete, not pseudo-code.Copy snippets directly into your project and adapt structure as needed.
Security-First Focus
Docs prioritize safe defaults: explicit CORS, strong JWT secrets, and health probes by default.
Architecture At A Glance
Client -> Selector accept loop -> Accepted SocketChannel (blocking mode for parser) -> Bounded worker pool -> HttpParser -> Router -> Middleware chain -> Handler / Plugin -> HttpResponse -> Client
- Requests are accepted by the NIO selector loop and then processed on bounded workers.
- Middleware executes in registration order for logging, CORS, metrics, rate limiting, and auth.
- Handlers operate on a typed HTTP context and return JSON/text with explicit status control.
- Optional persistence and asynchronous work offload keep IO handling responsive.
- Ops endpoints (health, readiness, metrics) integrate with monitors and rollout checks.
Performance Baselines
View full report →Throughput
501 req/s
p50 Latency
1.52 ms
p99 Latency
74.6 ms
Success Rate
99.84%