From 03e9a49c35457322cbb2b757cb74e797bf841aa0 Mon Sep 17 00:00:00 2001 From: Timofey Date: Wed, 4 Sep 2024 10:24:27 +0300 Subject: [PATCH] up README and add CONTRIBUTING.md --- CONTRIBUTING.md | 33 ++++++++++++++++++++++++++++ README.md | 58 +++++++++++++++++++++++++++++++++++++++++++++---- 2 files changed, 87 insertions(+), 4 deletions(-) create mode 100644 CONTRIBUTING.md diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 0000000..22a2c4f --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,33 @@ +## Getting Started + +Repository [open issues are here](https://github.com/kinescope/mc/issues). In time, we'll tag issues that would make a good first pull request for new contributors. An easy way to get started helping the project is to *file an issue*. You can do that on the repository issues page by clicking on the green button at the right. Issues can include bugs to fix, features to add, or documentation that looks outdated. + +## Contributions + +We welcome contributions from everyone. + +Contributions should be made in the form of GitHub pull requests. Each pull request will +be reviewed by a core contributor (someone with permission to land patches) and either landed in the +main tree or given feedback for changes that would be required. + +## Pull Request Checklist + +- Branch from the master branch and, if needed, rebase to the current master + branch before submitting your pull request. If it doesn't merge cleanly with + master you may be asked to rebase your changes. + +- Commits should be as small as possible, while ensuring that each commit is + correct independently (i.e., each commit should compile and pass tests). + +- Don't put submodule updates in your pull request unless they are to landed + commits. + +- If your patch is not getting reviewed or you need a specific person to review + it, you can @-reply a reviewer asking for a review in the pull request or a + comment. + +- Add tests relevant to the fixed bug or new feature. + +## Conduct + +We follow the [Golang Code of Conduct](https://go.dev/conduct). \ No newline at end of file diff --git a/README.md b/README.md index 36714de..ddc563e 100644 --- a/README.md +++ b/README.md @@ -4,7 +4,15 @@ [![Go Report Card](https://goreportcard.com/badge/github.com/kinescope/mc)](https://goreportcard.com/report/github.com/kinescope/mc) [![godoc](https://img.shields.io/badge/docs-GoDoc-green.svg)](https://godoc.org/github.com/kinescope/mc) +This is a memcache client library for the Go programming language, which uses memcache's binary protocol and supports namespacing out of the box. +## Installing +To add this libraty to your project, just run: +```bash +go get github.com/kinescope/mc +``` + +## Example ```go package main @@ -20,19 +28,22 @@ func main() { cache, err := mc.New(&mc.Options{ Addrs: []string{"127.0.0.1:11211"}, DialTimeout: 500 * time.Millisecond, - KeyHashFunc: mc.XXXKeyHashFunc, + KeyHashFunc: mc.XXKeyHashFunc, // or mc.DefaultKeyHashFunc. Hash function to use for namespaces ConnMaxLifetime: 15 * time.Minute, MaxIdleConnsPerAddr: 20, }) if err != nil { log.Fatal(err) } + ctx, cancel := context.WithDeadline(context.Background(), time.Now().Add(time.Second)) defer cancel() + type example struct { A string B string } + var value mc.Value err = value.Marshal(example{ A: "A", @@ -41,13 +52,15 @@ func main() { if err != nil { log.Fatal(err) } + err = cache.Set(ctx, &mc.Item{ Key: "cache_key", Value: value, - }, mc.WithExpiration(1_800, 60) /*mc.WithMinUses(10),*/, mc.WithNamespace("video_id:xxx")) + }, mc.WithExpiration(1_800, 60) /*mc.WithMinUses(10),*/, mc.WithNamespace("my_namespace")) if err != nil { log.Fatal(err) } + i, err := cache.Get(ctx, "cache_key") if err != nil { log.Fatal(err) @@ -57,5 +70,42 @@ func main() { log.Fatal(err) } log.Println(v) -} -``` \ No newline at end of file +``` +#### Namespacing +Let's say you have a user with some user_id like `123`. Given a user and all his related keys, you want a one-stop switch to invalidate all of their cache entries at the same time. +With namespacing you need to add a `mc.WithNamespace` option when setting any user related key. +```go +// set user name for id +var userName mc.Value +err = userName.Marshal("John") +err = cache.Set(ctx, &mc.Item{ + Key: "123", + Value: userName, +}, mc.WithNamespace("user_123")) + +// set user email for name +var userEmail mc.Value +err = userEmail.Marshal("example@gmail.com") +err = cache.Set(ctx, &mc.Item{ + Key: "John", + Value: userEmail, +}, mc.WithNamespace("user_123")) +``` +Then invalidating all of the keys for a user with id `123` would be as easy as: +```go +cache.PurgeNamespace(ctx, "user_123") // both 123:John and John:example@gmail.com entries will be deleted +``` +Namespaces are hashed by default to prevent collisions. There are two available hash functions - `mc.XXKeyHashFunc`, witch uses xx-hash, and `mc.DefaultKeyHashFunc` - witch doesn't hash keys at all. + +For more info on namespaces see [memcache wiki](https://github.com/memcached/memcached/wiki/ProgrammingTricks#namespacing). + +#### Other options +- `mc.WithExpiration(exp, scale uint32)` - after expiration time passes, first request for an item will get a cache miss, any other request will get a hit in a time window of `scale` seconds. See [memcache wiki](https://github.com/memcached/memcached/wiki/ProgrammingTricks#scaling-expiration). +- `mc.WithMinUses(number uint32)` - if an item under the key has been set less than `number` of times, requesting an item will result in a cache miss. See [tests](https://github.com/kinescope/mc/blob/main/client_extend_test.go) for clarity. + +## Contributing + +For contributing see [`CONTRIBUTING.md`](https://github.com/kinescope/mc/CONTRIBUTING.md) + +## Licensing +The code in this project is licensed under MIT license. \ No newline at end of file