Question 1

How does Vestigo compare to Gorilla Mux for Go routing?

Accepted Answer

Vestigo offers faster performance with a radix tree and better CORS support, but Gorilla Mux has a larger ecosystem and more built-in features. Vestigo is ideal if you prioritize speed and framework independence, while Gorilla Mux suits those wanting community-driven extensions.

Question 2

Can I use Vestigo with my existing net/http handlers?

Accepted Answer

Yes, Vestigo is designed to be fully compatible with standard http.HandlerFunc, so you can drop it into existing applications without rewriting handlers. It embeds URL parameters into the request's Form for easy access.

Question 3

How to handle wildcard routes in Vestigo?

Accepted Answer

Use catch-all routes with '/*' syntax and access the matched path via vestigo.Param(r, '_name'), as shown in the README examples. This allows flexible routing for migration or dynamic paths.

Question 4

Does Vestigo support authentication middleware?

Accepted Answer

Yes, you can add custom middleware to routes, such as authentication, by passing functions to router methods like Get or Post. The README provides an example where middleware can break the chain if authentication fails.

Question 5

What's the performance impact of using Vestigo vs. httprouter?

Accepted Answer

Vestigo is slightly worse in performance than httprouter but offers advantages like standard handler compatibility and CORS support. The README benchmarks show it's about 2x slower than Echo/Gin but faster for setups avoiding framework lock-in.

Question 6

Is Vestigo good for microservices?

Accepted Answer

Yes, its lightweight, standalone nature and CORS features make it suitable for microservices, but you'll need to handle validation and other advanced routing needs externally due to missing built-in tools.

vestigo

What is vestigo?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions