nanoServe

nanoServe is a lightweight HTTP router written in Go. It provides a trie-based routing engine with support for middleware, multiple HTTP methods, and flexible route handling.

The goal of nanoServe is to remain simple, fast, and easy to extend while maintaining clean architectural separation between routing and execution.

---

Features

• Trie-based path matching
• Support for all standard HTTP methods
• Global and path-specific middleware
• Variadic handler support
• Implements http.Handler interface
• Minimal and extensible core design
• Inbuilt param parser inside Trie router

---

Installation

go get github.com/libsib/nanoserve

---

Quick Start

package main

import (
	"net/http"
	"github.com/libsib/nanoserve"
)

func main() {
	r := nanoserve.New()

	globalMiddleware := func(c *nanoserve.Context) error {
		fmt.println("path: ", c.Request.URL.Path)
		c.Next() // it's necessary if you wants to invoke next handlers
		return nil
	}
	r.Use(globalMiddleware)
	r.GET("/hello", func(c *nanoserve.Context) error {
		c.Text("Hello World",200) // return c.Text("Hello World",200)
		// OR
		return nil
	})

	r.Run(":8080")
}

Visit http://localhost:8080/hello

---

Supported HTTP Methods

nanoServe supports all standard HTTP methods:

• GET
• POST
• PUT
• PATCH
• DELETE
• HEAD
• OPTIONS
• CONNECT
• TRACE

You can also use:

r.Handle(method, path, handlers...)
r.ANY(path, handlers...)

---

Middleware

Global Middleware

r.Use(func(c *nanoserve.Context) {
	println("global middleware")
})

Path-Specific Middleware

r.Use("/api", func(c *nanoserve.Context) error {
	println("api middleware")
	return nil
})

Middleware executes in the order they are registered.

---

Route Parameters

nanoServe supports parameterized routes using : prefix.

Example:

r.GET("/users/:id", handler)

Parameter extraction logic is handled by the trie router.

---

Architecture Overview

nanoServe follows a layered architecture:

1. HTTP Layer – Implements http.Handler
2. Router Layer – Manages route registration
3. Trie Layer – Handles path matching
4. Middleware Layer – Collects and executes middleware

This separation ensures maintainability and extensibility.

---

Project Structure

nanoserve/
├── router.go
├── trie.go
├── server.go
├── middleware.go
├── context.go (planned)

---

Roadmap

• Context abstraction
• Improved middleware chaining
• Route groups
• Subrouters
• 405 Method Not Allowed support
• Automatic OPTIONS handling
• Performance benchmarking

---

Philosophy

nanoServe aims to:

• Keep the core minimal
• Avoid unnecessary abstractions
• Maintain clean separation of concerns
• Stay idiomatic to Go
• Lazy work to keep nanoServe fast

---

License

MIT License

---

Contributing

Contributions are welcome. Feel