What are the recommended connection pool libraries written in Golang？

• examples

  2 9 0.0 Go

  examples for demonstrating Ergo Framework features (by ergo-services)

  

You didn't even try Ergo but made a lot of conclusions about this project. Golang is a statically typed language. So, you need to register the type of your message for sending over the network. For local communication, you just cast it to the type of expected message. Please, spend a bit of your time at least on the examples https://github.com/ergo-services/examples (especially this one https://github.com/ergo-services/examples/tree/master/cloud - just one concrete example)

• ergo

  32 2,660 1.7 Go

  An actor-based Framework with network transparency for creating event-driven architecture in Golang. Inspired by Erlang. Zero dependencies.

  

I think you should clarify what exactly you need. If you need something like TCP/UDP socket acceptor pool you may want to try Ergo Framework with ready to use design patterns https://github.com/ergo-services/ergo . Example for TCP https://github.com/ergo-services/examples/tree/master/gentcp, for UDP https://github.com/ergo-services/examples/tree/master/genudp

• InfluxDB

  www.influxdata.com sponsored

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• pool

  1 23 3.6 Go

  common golang tcp connection pool (by go-baa)

  

• sijsop

  5 13 3.7 Go

  A simple JSON-based protocol for Go, easy to implement for other languages

Moreover, because Ergo imports Erlang wholesale, it precludes things where you can send messages over the network and keep their types. Here's one simple example from a library of mine but there are numerous other options, gRPC, protocol buffers, etc. (I link this not because it is amazing code, but just because I have it on hand and personally know where it is. Also, note that as a demo program it demonstrates both typed and untyped receive; the "right" side does an untyped receive on purpose.) It is not necessary to lose types in general to go over a network.

Suggest a related project