We released Hazelcast Go Client v1.0.0.
This is the first major release of the revamped Go client. Of course the biggest news is, the client is compatible with Hazelcast 4.x and the upcoming Hazelcast 5.x. Here are the features included in this release:
- Distributed Data Structures: Map, Replicated Map, Queue, Topic, List, Set, PNCounter,
- Map aggregations,
- Improved Map locks,
- Load balancer,
- External client public address discovery,
- Lifecycle, cluster membership and distributed object listeners,
- Smart routing,
- Ownerless client,
- JSON, Identified Data, Portable and Global serialization,
- SSL connections (requires Hazelcast Enterprise),
- Username/password credentials (requires Hazelcast Enterprise),
- Hazelcast Management Center integration,
- Hazelcast Cloud integration,
- JSON configuration.
There are some missing features which exist in Go Client v0.6.0, such as the Near Cache, but we will complete them in the coming months, prioritized by the needs of our users.
Apart from Hazelcast 4.x+ compatibility, we aimed to implement conventions and best practices of the Go ecosystem. Here are some of the highlights:
- Go context: Enables Go client to play well with other libraries that support the context package. Any client function call can be canceled manually or after a deadline. This was one of the most wanted features of the new Go client.
- Go modules: Enables depending on a specific release without third party tools.
- Idiomatic errors: The client library returns errors which can be easily unwrapped using the standard errors package.
- Zero value configuration: The zero value of client configuration is the default configuration. Apart from being encouraged in idiomatic Go, it helps us provide a natural way of supporting JSON configuration.
- Package based code layout: The client code is split into logical packages which collect relevant code together, such as cluster, aggregate, serialization, types and others.
Some useful links:
We are looking forward to feedback in order to provide the features our users want. Join us at our Slack channel at Hazelcast Community
Oldest comments (0)