Skip to content

Valkey-Glide Go client GA release announcement blog #253

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

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

niharikabhavaraju
Copy link
Contributor

@niharikabhavaraju niharikabhavaraju commented Apr 30, 2025

Description

In the blog we will be discussing the GA release announcement for go client for Valkey GLIDE and sharing some design/methods we took, and some code snippets to encourage users to try.

Issues Resolved

Check List

  • Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the BSD-3-Clause License.

Signed-off-by: Niharika Bhavaraju <[email protected]>
@niharikabhavaraju niharikabhavaraju changed the title Valkey-Glide Go client transaction blog Valkey-Glide Go client GA release announcement blog May 8, 2025
Signed-off-by: Niharika Bhavaraju <[email protected]>
Copy link
Member

@stockholmux stockholmux left a comment

Choose a reason for hiding this comment

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

This is a great blog post!

The intro and conclusion need the most attention, but otherwise it's mostly small changes.

@@ -0,0 +1,503 @@
+++
title= "Valkey Glide Go Client: Now Generally Available!"
Copy link
Member

Choose a reason for hiding this comment

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

We should change 'go' to 'golang' a few times in this blog. I'll leave it up to you where, but the word 'go' is invisible to search engines.

Copy link
Member

@stockholmux stockholmux May 22, 2025

Choose a reason for hiding this comment

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

In this post you use "Valkey Glide", "Valkey GLIDE", and "valkey-glide". This should be consistent - the glide repo uses "Valkey GLIDE"

authors= [ "niharikabhavaraju"]
+++

Valkey-Glide is pleased to announce the the general availability (GA) release of the GLIDE(General Language Independent Driver for the Enterprise) Go client. This release brings the power and reliability of Valkey to Go developers with an API designed for performance and developer productivity.
Copy link
Member

Choose a reason for hiding this comment

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

Don't anthropomorphize "Valkey-Glide" - it's not a living thing and cannot announce anything. :)

Refactor to something like "The Valkey Glide team" or "The Valkey Glide contributors" instead.

Copy link
Member

Choose a reason for hiding this comment

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

Spacing: 'GLIDE(General Language Independent Driver for the Enterprise)' to 'GLIDE (General Language Independent Driver for the Enterprise)'

Copy link
Member

Choose a reason for hiding this comment

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

"the the" - edit.


Valkey-Glide is pleased to announce the the general availability (GA) release of the GLIDE(General Language Independent Driver for the Enterprise) Go client. This release brings the power and reliability of Valkey to Go developers with an API designed for performance and developer productivity.

Valkey GLIDE is a multi-language client for Valkey, designed for operational excellence and incorporating best practices refined through years of experience. GLIDE ensures a consistent and unified client experience across applications, regardless of the programming language.
Copy link
Member

Choose a reason for hiding this comment

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

I would drop this - it's not related to the topic of the post (Glide is available for Go) and it's a restatement of something that already said on the website. Maybe find a place the to link the text 'Valkey GLIDE' to a page that communicates what GLIDE is?


Valkey GLIDE is a multi-language client for Valkey, designed for operational excellence and incorporating best practices refined through years of experience. GLIDE ensures a consistent and unified client experience across applications, regardless of the programming language.

With support for Java, Node.js, Python, and now Go moving from public preview to general availability, this announcement introduces the Valkey GLIDE support for Go, expanding support to Go developers and providing new connectivity to Valkey servers, including both standalone and cluster deployments.
Copy link
Member

Choose a reason for hiding this comment

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

This is a bit confusing - it kind of sounds like Java/Node.js/Python are also going from public preview to GA as well. I think I would drop it as a standalone statement.

The important message in this line is about the other languages (Java, Node, Python). I would revise the first paragraph (line 8) to integrate the language message.

Is there something else that you're trying to communicate?

Copy link
Member

Choose a reason for hiding this comment

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

You say "Valkey servers" here and several other places - but the Valkey GitHub repo says valkey and redis. For obvious reasons, explicitly stating "that other support" support might not be great on this webiste, but I think it would be wise to be less specific to "Valkey servers"


With support for Java, Node.js, Python, and now Go moving from public preview to general availability, this announcement introduces the Valkey GLIDE support for Go, expanding support to Go developers and providing new connectivity to Valkey servers, including both standalone and cluster deployments.

## Why You Should Be Excited
Copy link
Member

Choose a reason for hiding this comment

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

Drop this heading.

}
```

In cluster transactions, the routing option does not enable multi-node transaction execution.
Copy link
Member

Choose a reason for hiding this comment

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

How important is this? It gets lost below the example.

In general, this type of writing isn't great for "does not" messages - your announcing what something is not what it can't do.


### Command Transparency

A key design followed is that commands can be used the same way in both regular and transaction contexts:
Copy link
Member

Choose a reason for hiding this comment

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

'A key design followed' is a bit awkward, feels like it is missing something (Also 'key' means something in the Valkey context, adding to confusion).

Do you mean a 'design concept', 'design pattern', or 'design principle'?

I like what you called it in the heading. Maybe revise to something like: "A important principle in the design of the client was transparently accessing the command, in both regular and transactions contexts"

cmd.Set("key1", "value1") // Queued for later execution
```

- Regular clients and transactions both implement a common interface
Copy link
Member

Choose a reason for hiding this comment

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

I would make these bullet points into a sentence/paragraph and move it above the example.


Valkey's optimistic locking mechanism is supported through:

- Implementation of `Watch()` that monitors keys for changes
Copy link
Member

Choose a reason for hiding this comment

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

add commas and a period as needed for each bullet point.


## Looking Forward

As we move toward general availability, we'll be expanding command support, enhancing performance, and adding even more features to make the Valkey GLIDE Go client a great choice for Go developers.
Copy link
Member

Choose a reason for hiding this comment

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

  • "As we move toward general availability"... wait - isn't this announcing GA not moving towards it.
  • "expanding command support" you say earlier that you've got all the commands: which is it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants