tidwall/evio is an open-source project on GitHub with 6.0k stars, written primarily in Go. Fast event-loop networking for Go
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
evio is an event loop networking framework that is fast and small. It makes direct epoll and kqueue syscalls rather than using the standard Go net package, and works in a similar manner as libuv and libevent.
The goal of this project is to create a server framework for Go that performs on par with Redis and Haproxy for packet handling. It was built to be the foundation for Tile38 and a future L7 proxy for Go.
Please note: Evio should not be considered as a drop-in replacement for the standard Go net or net/http packages.
Features
Fast single-threaded or multithreaded event loop
Built-in load balancing options
Simple API
Low memory usage
Supports tcp, udp, and unix sockets
Allows multiple network binding on the same event loop
Flexible ticker event
Fallback for non-epoll/kqueue operating systems by simulating events with the net package
SO_REUSEPORT socket option
Getting Started
Installing
To start using evio, install Go and run go get:
$ go get -u github.com/tidwall/evio
This will retrieve the library.
Usage
Starting a server is easy with evio. Just set up your events and pass them to the Serve function along with the binding address(es). Each connections is represented as an evio.Conn object that is passed to various events to differentiate the clients. At any point you can close a client or shutdown the server by return a Close or Shutdown action from an event.
Example echo server that binds to port 5000:
package main
import "github.com/tidwall/evio"
func main() {
var events evio.Events
events.Data = func(c evio.Conn, in []byte) (out []byte, action evio.Action) {
out = in
return
}
if err := evio.Serve(events, "tcp://localhost:5000"); err != nil {
panic(err.Error())
}
}
Here the only event being used is Data, which fires when the server receives input data from a client.
The exact same input data is then passed through the output return value, which is then sent back to the client.
Connect to the echo server:
$ telnet localhost 5000
Events
The event type has a bunch of handy events:
Serving fires when the server is ready to accept new connections.
Opened fires when a connection has opened.
Closed fires when a connection has closed.
Detach fires when a connection has been detached using the Detach return action.
Data fires when the server receives new data from a connection.
Tick fires immediately after the server starts and will fire again after a specified interval.
Multiple addresses
A server can bind to multiple addresses and share the same event loop.
All incoming and outgoing packets are not buffered and sent individually.
The Opened and Closed events are not availble for UDP sockets, only the Data event.
Multithreaded
The events.NumLoops options sets the number of loops to use for the server.
A value greater than 1 will effectively make the server multithreaded for multi-core machines.
Which means you must take care when synchonizing memory between event callbacks.
Setting to 0 or 1 will run the server as single-threaded.
Setting to -1 will automatically assign this value equal to runtime.NumProcs().
Load balancing
The events.LoadBalance options sets the load balancing method.
Load balancing is always a best effort to attempt to distribute the incoming connections between multiple loops.
This option is only available when events.NumLoops is set.
Random requests that connections are randomly distributed.
RoundRobin requests that connections are distributed to a loop in a round-robin fashion.
LeastConnections assigns the next accepted connection to the loop with the least number of active connections.
SO_REUSEPORT
Servers can utilize the SO_REUSEPORT option which allows multiple sockets on the same host to bind to the same port.
No homepage URL was recorded for tidwall/evio in TopGit's last sync. The README tab above frequently contains screenshots and demo links, or check the repository description on GitHub.
How active is development on tidwall/evio?
The most recent commit recorded on tidwall/evio was 6 months ago, based on the GitHub push timestamp. The repository has 489 forks — one of the better signals of community interest.
How many stars does tidwall/evio have?
tidwall/evio has 6.0k GitHub stars — refresh the page for the live number, or check github.com/tidwall/evio. TopGit mirrors GitHub's count but does not claim minute-by-minute accuracy.
What language is tidwall/evio written in?
tidwall/evio is written primarily in Go. GitHub's language field is based on the largest share of bytes in the default branch.
What license does tidwall/evio use?
tidwall/evio is released under the MIT license. Always verify the LICENSE file directly on GitHub for the authoritative terms — license strings can be edited out of sync with a project's actual stance.
What topics is tidwall/evio associated with?
GitHub's repository topics for tidwall/evio: "networking". TopGit's editorial category is open-source.
Where do I read more about tidwall/evio?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/tidwall/evio is the definitive source.
Read full README in the tab above.
Curious whether evio is right for you?
Let ChatGPT, Claude, or Perplexity look into it — click below and see what AI actually says about evio.