clickhouse-go alternatives and similar packages
Based on the "Search and Analytic Databases" category.
Alternatively, view clickhouse-go alternatives based on common mentions on social networks and blogs.
-
elastic
Deprecated: Use the official Elasticsearch client for Go at https://github.com/elastic/go-elasticsearch
SaaSHub - Software Alternatives and Reviews
Do you think we are missing an alternative of clickhouse-go or a related project?
README
ClickHouse
Golang SQL database client for ClickHouse.
Versions
There are two version of this client, v1 and v2, available as separate branches.
v1 is now in a state of a maintenance - we will only accept PRs for bug and security fixes.
Users should use v2 which is production ready and significantly faster than v1.
v2 has breaking changes for users migrating from v1. These were not properly tracked prior to this client being officially supported. We endeavour to track known differences here and resolve where possible.
Supported ClickHouse Versions
The client is tested against the currently supported versions of ClickHouse
Supported Golang Versions
Client Version | Golang Versions |
---|---|
=> 2.0 <= 2.2 | 1.17, 1.18 |
>= 2.3 | 1.18.4+, 1.19 |
Key features
- Uses ClickHouse native format for optimal performance. Utilises low level ch-go client for encoding/decoding and compression (versions >= 2.3.0).
- Supports native ClickHouse TCP client-server protocol
- Compatibility with
database/sql
(slower than native interface!) database/sql
supports http protocol for transport. (Experimental)- Marshal rows into structs ([ScanStruct](examples/clickhouse_api/scan_struct.go), [Select](examples/clickhouse_api/select_struct.go))
- Unmarshal struct to row ([AppendStruct](benchmark/v2/write-native-struct/main.go))
- Connection pool
- Failover and load balancing
- [Bulk write support](examples/clickhouse_api/batch.go) (for
database/sql
[use](examples/std/batch.go)begin->prepare->(in loop exec)->commit
) - [AsyncInsert](benchmark/v2/write-async/main.go)
- Named and numeric placeholders support
- LZ4/ZSTD compression support
- External data
Support for the ClickHouse protocol advanced features using Context
:
- Query ID
- Quota Key
- Settings
- OpenTelemetry
- Execution events:
- Logs
- Progress
- Profile info
- Profile events
Documentation
https://clickhouse.com/docs/en/integrations/go
clickhouse
interface (formally native
interface)
conn, err := clickhouse.Open(&clickhouse.Options{
Addr: []string{"127.0.0.1:9000"},
Auth: clickhouse.Auth{
Database: "default",
Username: "default",
Password: "",
},
DialContext: func(ctx context.Context, addr string) (net.Conn, error) {
dialCount++
var d net.Dialer
return d.DialContext(ctx, "tcp", addr)
},
Debug: true,
Debugf: func(format string, v ...interface{}) {
fmt.Printf(format, v)
},
Settings: clickhouse.Settings{
"max_execution_time": 60,
},
Compression: &clickhouse.Compression{
Method: clickhouse.CompressionLZ4,
},
DialTimeout: time.Duration(10) * time.Second,
MaxOpenConns: 5,
MaxIdleConns: 5,
ConnMaxLifetime: time.Duration(10) * time.Minute,
ConnOpenStrategy: clickhouse.ConnOpenInOrder,
BlockBufferSize: 10,
})
if err != nil {
return err
}
return conn.Ping(context.Background())
database/sql
interface
OpenDB
conn := clickhouse.OpenDB(&clickhouse.Options{
Addr: []string{"127.0.0.1:9999"},
Auth: clickhouse.Auth{
Database: "default",
Username: "default",
Password: "",
},
TLS: &tls.Config{
InsecureSkipVerify: true,
},
Settings: clickhouse.Settings{
"max_execution_time": 60,
},
DialTimeout: 5 * time.Second,
Compression: &clickhouse.Compression{
clickhouse.CompressionLZ4,
},
Debug: true,
BlockBufferSize: 10,
})
conn.SetMaxIdleConns(5)
conn.SetMaxOpenConns(10)
conn.SetConnMaxLifetime(time.Hour)
DSN
- hosts - comma-separated list of single address hosts for load-balancing and failover
- username/password - auth credentials
- database - select the current default database
- dial_timeout - a duration string is a possibly signed sequence of decimal numbers, each with optional fraction and a unit suffix such as "300ms", "1s". Valid time units are "ms", "s", "m".
- connection_open_strategy - round_robin/in_order (default in_order).
- round_robin - choose a round-robin server from the set
- in_order - first live server is chosen in specified order
- debug - enable debug output (boolean value)
- compress - compress - specify the compression algorithm - “none” (default),
zstd
,lz4
,gzip
,deflate
,br
. If set totrue
,lz4
will be used. - compress_level - Level of compression (default is 0). This is algorithm specific:
gzip
--2
(Best Speed) to9
(Best Compression)deflate
--2
(Best Speed) to9
(Best Compression)br
-0
(Best Speed) to11
(Best Compression)zstd
,lz4
- ignored
- block_buffer_size - size of block buffer (default 2)
SSL/TLS parameters:
- secure - establish secure connection (default is false)
- skip_verify - skip certificate verification (default is false)
Example:
clickhouse://username:password@host1:9000,host2:9000/database?dial_timeout=200ms&max_execution_time=60
HTTP Support (Experimental)
The native format can be used over the HTTP protocol. This is useful in scenarios where users need to proxy traffic e.g. using ChProxy or via load balancers.
This can be achieved by modifying the DSN to specify the http protocol.
http://host1:8123,host2:8123/database?dial_timeout=200ms&max_execution_time=60
Alternatively, use OpenDB
and specify the interface type.
conn := clickhouse.OpenDB(&clickhouse.Options{
Addr: []string{"127.0.0.1:8123"},
Auth: clickhouse.Auth{
Database: "default",
Username: "default",
Password: "",
},
Settings: clickhouse.Settings{
"max_execution_time": 60,
},
DialTimeout: 5 * time.Second,
Compression: &clickhouse.Compression{
Method: clickhouse.CompressionLZ4,
},
Interface: clickhouse.HttpInterface,
})
Compression
ZSTD/LZ4 compression is supported over native and http protocols. This is performed at a block level and is only used for inserts.
If using Open
via the std interface and specifying a DSN, compression can be enabled via the compress
flag. Currently, this is a boolean flag which enables LZ4
compression.
Other compression methods will be added in future PRs.
TLS/SSL
At a low level all client connect methods (DSN/OpenDB/Open) will use the Go tls package to establish a secure connection. The client knows to use TLS if the Options struct contains a non-nil tls.Config pointer.
Setting secure in the DSN creates a minimal tls.Config struct with only the InsecureSkipVerify field set (either true or false). It is equivalent to this code:
conn := clickhouse.OpenDB(&clickhouse.Options{
...
TLS: &tls.Config{
InsecureSkipVerify: false
}
...
})
This minimal tls.Config is normally all that is necessary to connect to the secure native port (normally 9440) on a ClickHouse server. If the ClickHouse server does not have a valid certificate (expired, wrong host name, not signed by a publicly recognized root Certificate Authority), InsecureSkipVerify can be to true
, but that is strongly discouraged.
If additional TLS parameters are necessary the application code should set the desired fields in the tls.Config struct. That can include specific cipher suites, forcing a particular TLS version (like 1.2 or 1.3), adding an internal CA certificate chain, adding a client certificate (and private key) if required by the ClickHouse server, and most of the other options that come with a more specialized security setup.
HTTPS (Experimental)
To connect using HTTPS either:
Use
https
in your dsn string e.g.https://host1:8443,host2:8443/database?dial_timeout=200ms&max_execution_time=60
Specify the interface type as
HttpsInterface
e.g.
conn := clickhouse.OpenDB(&clickhouse.Options{
Addr: []string{"127.0.0.1:8443"},
Auth: clickhouse.Auth{
Database: "default",
Username: "default",
Password: "",
},
Interface: clickhouse.HttpsInterface,
})
Benchmark
[V1 (READ)](benchmark/v1/read/main.go) | [V2 (READ) std](benchmark/v2/read/main.go) | [V2 (READ) clickhouse API](benchmark/v2/read-native/main.go) |
---|---|---|
1.218s | 924.390ms | 675.721ms |
[V1 (WRITE)](benchmark/v1/write/main.go) | [V2 (WRITE) std](benchmark/v2/write/main.go) | [V2 (WRITE) clickhouse API](benchmark/v2/write-native/main.go) | [V2 (WRITE) by column](benchmark/v2/write-native-columnar/main.go) |
---|---|---|---|
1.899s | 1.177s | 699.203ms | 661.973ms |
Install
go get -u github.com/ClickHouse/clickhouse-go/v2
Examples
native interface
- [batch](examples/clickhouse_api/batch.go)
- [async insert](examples/clickhouse_api/async.go)
- [batch struct](examples/clickhouse_api/append_struct.go)
- [columnar](examples/clickhouse_api/columnar_insert.go)
- [scan struct](examples/clickhouse_api/scan_struct.go)
- [bind params](examples/clickhouse_api/bind.go)
std database/sql
interface
- [batch](examples/std/batch.go)
- [async insert](examples/std/async.go)
- [open db](examples/std/connect.go)
- [bind params](examples/std/bind.go)
ClickHouse alternatives - ch-go
Versions of this client >=2.3.x utilise ch-go for their low level encoding/decoding. This low lever client provides a high performance columnar interface and should be used in performance critical use cases. This client provides more familar row orientated and database/sql
semantics at the cost of some performance.
Both clients are supported by ClickHouse.
Third-party alternatives
Database client/clients:
- mailru/go-clickhouse (uses the HTTP protocol)
- uptrace/go-clickhouse (uses the native TCP protocol with
database/sql
-like API) - Drivers with columnar interface:
Insert collectors: