A framework for constructing high performance, modular HTTP servers in Go. Read more on our blog »

• Modular and flexible design
• Hot restart hooks for zero-downtime deploys
• Builtin statistics framework
• Builtin logging framework

Falcore is a filter pipeline based HTTP server library. You can build arbitrarily complicated HTTP services by chaining just a few simple components:

• RequestFilters are the core component. A request filter takes a request and returns a response or nil. Request filters an modify the request as it passes through.
• ResponseFilters can modify a response on its way out the door. An example response filter, compression_filter, is included. It applies deflate or gzip compression to the response if the request supplies the proper headers.
• Pipelines form one of the two logic components. A pipeline contains a list of RequestFilters and a list of ResponseFilters. A request is processed through the request filters, in order, until one returns a response. It then passes the response through each of the response filters, in order. A pipeline is a valid RequestFilter.
• Routers allow you to conditionally follow different pipelines. A router chooses from a set of pipelines. A few basic routers are included, including routing by hostname or requested path. You can implement your own router by implementing falcore.Router. Routers are not RequestFilters, but they can be put into pipelines.

Falcore currently depends on gb to build. Falcore can be installed with gb -i or submoduled into a project. It is not currently compatible with goinstall.

Falcore is currently targeted at Go release r.60.3.

See the examples directory for usage examples.

To use falcore to serve HTTPS, simply call ListenAndServeTLS instead of ListenAndServe. If you want to host SSL and nonSSL out of the same process, simply create two instances of falcore.Server. You can give them the same pipeline or share pipeline components.

• Dave Grijalva
• Scott White