How to handle authentication in ozzo-routing?

Use built-in handlers like auth.JWT or auth.Basic from the subpackages. For example, add auth.JWT as middleware in a route group to secure endpoints.

ozzo-routing vs gin: which should I use?

Choose ozzo-routing for Express-like middleware and standard library compatibility; gin offers a larger ecosystem and more built-in features like rendering. Both are high-performance.

How to serve static files with ozzo-routing?

Use the file.Server handler for directories or file.Content for single files, as shown in the README example with router.Get("/*", file.Server(...)).

Does ozzo-routing support WebSockets?

No, it's designed for HTTP routing only. You'll need to use additional packages like gorilla/websocket and integrate them separately with your server.

How to implement custom middleware in ozzo-routing?

Define a function with signature func(*routing.Context) error and register it using router.Use() for global middleware or group.Use() for route-specific middleware.

What's the performance difference between ozzo-routing and httprouter?

Benchmarks in the README show comparable speed with zero allocations; ozzo-routing adds middleware flexibility while httprouter is more minimalist.

Open-Awesome

ozzo-routing

MITGov2.4.0

An extremely fast Go HTTP router with regex route matching and full RESTful API support.

GitHub

451 stars48 forks0 contributors

What is ozzo-routing?

Ozzo-routing is a Go package that provides high-performance HTTP routing for web applications. It features a middleware pipeline architecture, supports regular expression route matching, and includes built-in handlers for building RESTful APIs. It solves the need for a fast, flexible router that integrates well with Go's standard library.

Target Audience

Go developers building web applications or RESTful APIs who need a performant and feature-rich routing solution. It's particularly suitable for projects requiring regex-based routing, middleware pipelines, and compatibility with existing `http.Handler` patterns.

Value Proposition

Developers choose ozzo-routing for its exceptional speed (zero dynamic allocations), Express-like middleware flexibility, and comprehensive built-in handlers. It offers a pragmatic balance between performance and productivity without locking users into a full-stack framework.

Overview

An extremely fast Go (golang) HTTP router that supports regular expression route matching. Comes with full support for building RESTful APIs.

Use Cases

Best For

Building high-performance RESTful APIs in Go
Implementing middleware pipelines for request processing
Applications requiring regex-based URL parameter matching
Projects needing route grouping for modular code organization
Servers that must remain compatible with standard http.Handler interfaces
Scenarios where low memory allocation and fast routing are critical

Not Ideal For

Projects requiring a full-stack web framework with built-in ORM, templating, or session management
Teams that need automatic OpenAPI/Swagger documentation generation out of the box
Applications heavily reliant on WebSocket or real-time communication protocols
Developers preferring routers with maximalist features like built-in validation or serialization libraries

Pros & Cons

Pros

Extreme Performance

Benchmarks show zero dynamic memory allocation and routing speed comparable to httprouter and gin, making it ideal for high-throughput APIs.

Middleware Pipeline

Express-like architecture allows modular and reusable request handling, with built-in handlers for logging, CORS, and error recovery.

Standard Library Compatibility

Seamlessly works with standard http.Handler and http.HandlerFunc, easing integration into existing Go codebases.

Flexible Route Matching

Supports URL parameters and regular expressions in route definitions, enabling complex routing logic without extra dependencies.

Cons

Limited Built-in Features

As a routing package, it lacks advanced features like input validation, serialization, or API documentation tools, requiring additional libraries.

Smaller Ecosystem

Third-party handlers and extensions are fewer compared to more popular routers like gin or echo, potentially increasing development time for custom needs.

No Native WebSocket Support

Focused on HTTP routing, it doesn't provide built-in support for WebSockets or other protocols, necessitating separate integrations.

Frequently Asked Questions

Related Projects

Chi

lightweight, idiomatic and composable router for building Go HTTP services

Stars22,790

Forks1,160

Last commit8 days ago

mux

Package gorilla/mux is a powerful HTTP router and URL matcher for building Go web servers with 🦍

Stars21,843

Forks1,893

Last commit2 years ago

httprouter

A high performance HTTP request router that scales well

Stars17,129

Forks1,464