Falcore is a framework for constructing high performance, modular HTTP servers in Go (sometimes called Golang).
Falcore's architecture consists of an upstream pipeline where stages are run in sequence until a stage returns an HTTP Response. There is a separate downstream pipeline which runs against the response before it is returned to the client. Any stage may be arbitrarily complex, but you'll get extra benefits from breaking your application up into separate modules spread out over stages.
An example request might encounter several filters while traversing a pipeline:
One central benefit to pipelining approach is that it allows for code re-use. Included in the repositories are filters for performing common HTTP server tasks such as response compression, etag matching, and serving files from disk. Each of these filters, and any filters you write yourself, can easily be dropped into any Falcore pipeline. Simply compose the features you want and start your server.
net/httpand Google App Engine
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 can 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
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
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
Routers are not
RequestFilters, but they can be put into pipelines.
examples directory for usage examples.
go get github.com/fitstar/falcore.
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.
Falcore is currently targeted at Go 1.1. There are no dependencies outside the standard library.
If you would like to help out, just send a pull request. Patches are far more likely to be accepted if they include tests, but don't be shy about opening a pull request to get a conversation going. If you would like to discuss your idea before spending a bunch of time on it, open an issue.