Categorygithub.com/lonng/nano
modulepackage
0.5.1
Repository: https://github.com/lonng/nano.git
Documentation: pkg.go.dev

# README

Nano Build Status GoDoc Go Report Card MIT licensed

Nano is an easy to use, fast, lightweight game server networking library for Go. It provides a core network architecture and a series of tools and libraries that can help developers eliminate boring duplicate work for common underlying logic. The goal of nano is to improve development efficiency by eliminating the need to spend time on repetitious network related programming.

Nano was designed for server-side applications like real-time games, social games, mobile games, etc of all sizes.

How to build a system with Nano

What does a Nano application look like?

The simplest "nano" application as shown in the following figure, you can make powerful applications by combining different components.

Application

In fact, the nano application is a collection of  Component , and a component is a bundle of  Handler, once you register a component to nano, nano will register all methods that can be converted to Handler to nano service container. Service was accessed by Component.Handler, and the handler will be called while client request. The handler will receive two parameters while handling a message:

  • *session.Session: corresponding a client that apply this request or notify.
  • *protocol.FooBar: the payload of the request.

While you had processed your logic, you can response or push message to the client by session.Response(payload) and session.Push('eventName', payload), or returns error when some unexpected data received.

How to build distributed system with Nano

Nano contains built-in distributed system solution, and make you creating a distributed game server easily.

See: The distributed chat demo

The Nano will remain simple, but you can perform any operations in the component and get the desired goals. You can startup a group of Nano application as agent to dispatch message to backend servers.

How to execute the asynchronous task

func (manager *PlayerManager) Login(s *session.Session, msg *ReqPlayerLogin) error {
    var onDBResult = func(player *Player) {
        manager.players = append(manager.players, player)
        s.Push("PlayerSystem.LoginSuccess", &ResPlayerLogin)
    }
    
    // run slow task in new gorontine
    go func() {
        player, err := db.QueryPlayer(msg.PlayerId) // ignore error in demo
        // handle result in main logical gorontine
        nano.Invoke(func(){ onDBResult(player) })
    }
    return nil
}

Documents

Resources

Community

Successful cases

Go version

> go1.8

Installation

go get github.com/lonng/nano

# dependencies
go get -u github.com/pingcap/check
go get -u github.com/pingcap/errors
go get -u github.com/urfave/cli

go get -u google.golang.org/protobuf/proto
go get -u github.com/gorilla/websocket
go get -u google.golang.org/grpc

Protocol Buffers

# protoc
# download form: https://github.com/protocolbuffers/protobuf/releases
# protoc-gen-go
go install google.golang.org/protobuf/cmd/protoc-gen-go@latest
go install google.golang.org/grpc/cmd/protoc-gen-go-grpc@latest
# delve
go install github.com/go-delve/delve/cmd/dlv@latest

Test

go test -v ./...

Benchmark

# Case:   PingPong
# OS:     Windows 10
# Device: i5-6500 3.2GHz 4 Core/1000-Concurrent   => IOPS 11W(Average)
# Other:  ...

cd ./benchmark/io
go test -v -tags "benchmark"

License

MIT License

# Packages

# Functions

Listen listens on the TCP network address addr and then calls Serve with handler to handle requests on incoming connections.
NewGroup returns a new group instance.
Shutdown send a signal to let 'nano' shutdown itself.
WithAdvertiseAddr sets the advertise address option, it will be the listen address in master node and an advertise address which cluster member to connect.
WithCheckOriginFunc sets the function that check `Origin` in http headers.
WithMemberAddr sets the listen address which is used to establish connection between cluster members.
WithComponents sets the Components.
WithCustomerRemoteServiceRoute register remote service route.
WithDebugMode let 'nano' to run under Debug mode.
SetDictionary sets routes map.
WithGrpcOptions sets the grpc dial options.
WithHandshakeValidator sets the function that Verify `handshake` data.
WithHeartbeatInterval sets Heartbeat time interval.
WithIsWebsocket indicates whether current node WebSocket is enabled.
WithLabel sets the current node label in cluster.
WithLogger overrides the default logger.
WithMaster sets the option to indicate whether the current node is master node.
WithNodeId set nodeId use snowflake nodeId generate sessionId, default: pid.
WithSerializer customizes application serializer, which automatically Marshal and UnMarshal handler payload.
SetTimerPrecision sets the ticker precision, and time precision can not less than a Millisecond, and can not change after application running.
WithTSLConfig sets the `key` and `certificate` of TSL.
WithUnregisterCallback master unregister member event call fn.

# Variables

Errors that could be occurred during message handling.
Errors that could be occurred during message handling.
Errors that could be occurred during message handling.
Errors that could be occurred during message handling.
VERSION returns current nano version.

# Structs

Group represents a session group which used to manage a number of sessions, data send to the group will send to all session in it.

# Type aliases

SessionFilter represents a filter which was used to filter session when Multicast, the session will receive the message while filter returns true.