Skip to content

Valkey GLIDE for Go GA blog #277

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 13 commits into from
Closed
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update content/blog/2025-05-08-go-client-GA.md
Co-authored-by: Yury-Fridlyand <yury.fridlyand@improving.com>
Signed-off-by: Joseph Brinkman <joe.brinkman@improving.com>
  • Loading branch information
jbrinkman and Yury-Fridlyand authored Jun 18, 2025
commit c8a923788decdb4060668f21f402bfdeaf09baf7
2 changes: 1 addition & 1 deletion content/blog/2025-05-08-go-client-GA.md

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fix filename to the correct date

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That will get fixed with the actual release of the blog. Until we get final approval that is a moving date.

Original file line number Diff line number Diff line change
Expand Up @@ -353,7 +353,7 @@ Define a new batch using `pipeline.NewStandaloneBatch(isAtomic)` or `pipeline.Ne

## Cluster mode Batch

Cluster batches are similar to standalone batches, but they are executed on a cluster client. They may have specific routing options to control which node the commands are executed on. In a cluster batch, all commands are executed on the same node, unless the IsAtomic flag is set to false (i.e. is a pipeline and not a transaction), in which case the commands may be split based on the key slot. Once all commands have been executed, the results (including any errors) are returned to the client. For pipelines, the results are returned in the same order as the commands were queued, even when the commands are executed on different nodes.
Cluster batches are similar to standalone batches, but they are executed on a cluster client. They may have specific routing options to control which node the commands are executed on. In a cluster batch, all commands are executed on the same node, unless the `IsAtomic` flag is set to `false` (i.e. is a pipeline and not a transaction), in which case the commands may be split based on the key slot. Once all commands have been executed, the results (including any errors) are returned to the client. For pipelines, the results are returned in the same order as the commands were queued, even when the commands are executed on different nodes.

```go
// Cluster BatchClient Example
Expand Down