golax alternatives and similar packages
Based on the "Libraries for creating HTTP middlewares" category.
Alternatively, view golax alternatives based on common mentions on social networks and blogs.
InfluxDB - Purpose built for real-time analytics at any scale.
Do you think we are missing an alternative of golax or a related project?
Popular Comparisons
README
Golax is the official go implementation for the Lax framework.
<!-- MarkdownTOC autolink=true bracket=round depth=4 -->
- About Lax
- Getting started
- Routing example
- Performance
- How interceptor works
- Handling parameters
- Support for Google custom methods
- Sample use cases
<!-- /MarkdownTOC -->
Related docs:
- [Developer notes](doc/developer.md)
- [TODO list](doc/todo.md)
About Lax
Lax wants to be the best "user experience" for developers making REST APIs.
The design principles for Lax are:
- The lowest language overhead
- Extremely fast to develop
- Very easy to read and trace.
Getting started
my_api := golax.NewApi()
my_api.Root.
Interceptor(golax.InterceptorError).
Interceptor(myLogingInterceptor)
my_api.Root.Node("hello").
Method("GET", func(c *golax.Context) {
// At this point, Root interceptors has been already executed
fmt.Fprintln(c.Response, "Hello world!")
})
my_api.Serve()
Routing example
Routing is based on nodes.
There are three types: static
, regex
and parameter
.
- static: Only matches with the url part if it is exactly the same.
- regex: Surrounded by
(
and)
, if the regex match. - parameter: Surrounded by
{
and}
, always matches.
Performance
The performance compared with the most popular alternative is very similar (actually golax performs slightly better) however code readability and maintainability is far better with golax implementation.
Tests has been executed in a Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz
.
Learn more about this https://github.com/fulldump/golax-performance.
How interceptor works
If I want to handle a GET /users/1234/stats
request, all interceptors in nodes from <root>
to .../stats
are executed:
[Normal flow](doc/figure_1_normal_flow.png)
To abort the execution, call to c.Error(404, "Resource not found")
:
[Break flow](doc/figure_2_break_flow.png)
Handling parameters
my_api := golax.NewApi()
my_api.Root.
Node("users").
Node("{user_id}").
Method("GET", func (c *golax.Context) {
fmt.Fprintln(c.Response, "You are looking for user " + c.Parameter)
})
my_api.Serve()
It is also possible get all parameters:
func (c *golax.Context) {
fmt.Fprintln(c.Response, "All parameters:", c.Parameters)
}
Support for Google custom methods
According to Google's API design guidelines to map RPC services to REST HTTP, it describes custom methods as extra operations that can not be easyly mapped to HTTP verbs. More info about custom methods
For example, this URL has a custom method :activate
:
https://my.service.com/v1/users/31231231231:activate
Golax support custom methods as operations:
my_api.Root.
Node("v1").
Node("users").
Node("{user_id}").
Operation("activate").
Method("POST", func(c *golax.Context) {
user_id := c.Parameters["{user_id}"]"
fmt.Fprintln(c.Response, "Here is custom method ':activate' for user "+user_id)
})
Sample use cases
TODO: put here some examples to cover cool things:
- fluent implementation
- node cycling
- readability
- node preference
- sample logging interceptor
- sample auth interceptor
- sample api errors