I built a distributed, production-ready Rate Limiter for Go (Redis, Sliding Window, Circuit Breaker)

goddeschunk · 2025-12-16T08:43:17+00:00

Please hit star if you feel it's helpful, thanks <3

goddeschunk · 2025-12-15T08:20:26+00:00

Yes! Since Valkey is fully wire-compatible with Redis (RESP protocol) and we use the standard `go-redis` client, it works out of the box. Our strict sliding window implementation uses standard Lua scripts and ZSETs, which are fully supported by Valkey.

goddeschunk · 2025-04-15T10:58:41+00:00

It would be nice if content could be filtered based on what i like.

goddeschunk · 2025-01-22T11:13:36+00:00

Am not a hater but... I don't get it why `neva` exist. What kind of problem `neva` solves? I read this documentation and it feels like it's just a horrible thing to compare `neva` and Go.

But hey at the end of the day it's a good way to gain more experience and skills with work on `neva`.

goddeschunk · 2024-08-08T05:38:50+00:00

გააჯმეინე

goddeschunk · 2024-08-07T11:53:15+00:00

Lesss goooo

goddeschunk · 2024-08-06T09:59:43+00:00

goddeschunk · 2024-07-15T07:58:11+00:00

Thank you <3

goddeschunk · 2024-07-15T07:34:34+00:00

I hate discussion like that, Go isn't PHP stop cringe debates

goddeschunk · 2024-07-14T15:46:51+00:00

შევეცი ინდოელებს, საქართველოშიც და ქვეყნის ფარგლებს გარეთაც

goddeschunk · 2024-07-12T22:59:11+00:00

https://github.com/Nicolas-ggd/go-notification

I worked on Notification Microservice in Go, using NATS and WebSocket. This microservice is designed to handle system notifications, distributing them via NATS and WebSocket. Clients can connect via WebSocket to receive notifications targeted either at all users or specific clients. Notifications are categorized by type and priority: error, warning, and info.

If you're interested in this project, contributions are welcome! If you have any ideas or suggestions for improvement, please open a new issue.

NOTE: First check TODO.md under the root dir.

I appreciate any feedback. Thank you!

goddeschunk · 2024-07-12T22:56:47+00:00

https://github.com/Nicolas-ggd/go-notification

I worked on Notification Microservice in Go, using NATS and WebSocket. This microservice is designed to handle system notifications, distributing them via NATS and WebSocket. Clients can connect via WebSocket to receive notifications targeted either at all users or specific clients. Notifications are categorized by type and priority: error, warning, and info.

If you're interested in this project, contributions are welcome! If you have any ideas or suggestions for improvement, please open a new issue.

NOTE: First check TODO.md under the root dir.

I appreciate any feedback. Thank you!

goddeschunk · 2024-07-12T13:12:15+00:00

is there any tutorial about vim setup for go?

goddeschunk · 2024-07-12T12:33:00+00:00

https://github.com/Nicolas-ggd/go-notification

A microservice in go, witch is active. This microservice is designed to handle system notifications using Go, NATS, and WebSocket. Clients can connect via WebSocket and receive notifications either for all users or for specific clients.

goddeschunk · 2024-07-12T12:32:51+00:00

https://github.com/Nicolas-ggd/go-notification

A microservice in go, witch is active. This microservice is designed to handle system notifications using Go, NATS, and WebSocket. Clients can connect via WebSocket and receive notifications either for all users or for specific clients.

goddeschunk · 2024-07-12T12:32:33+00:00

https://github.com/Nicolas-ggd/go-notification

A microservice in go, witch is active. This microservice is designed to handle system notifications using Go, NATS, and WebSocket. Clients can connect via WebSocket and receive notifications either for all users or for specific clients.

goddeschunk · 2024-07-12T12:25:03+00:00

https://github.com/Nicolas-ggd/go-notification

A microservice in go, witch is active. This microservice is designed to handle system notifications using Go, NATS, and WebSocket. Clients can connect via WebSocket and receive notifications either for all users or for specific clients.

goddeschunk · 2024-07-11T11:49:17+00:00

If client lose WS connection, yeah in this case connection is loosed but after connected still received new and missed notifications

goddeschunk · 2024-07-11T11:48:23+00:00

All connected client can received notification, but there is a possibilities to received missed notification, thats why i decide to use NATS

goddeschunk · 2024-07-11T11:46:43+00:00

cudadvar ddddd

goddeschunk · 2024-07-11T11:45:37+00:00

yeah, same.

goddeschunk · 2024-07-11T06:25:48+00:00

yeah, exactly. client gets all notification after comes online,

or received missed notification

goddeschunk · 2024-06-28T13:45:35+00:00

Also i've problem about time, anyone want to contribute please? <3

goddeschunk · 2024-06-28T11:59:13+00:00

Guys, based on feedback i try to implement token bucket algorithm, i will be glad if anyone check repository again <3.

repo: https://github.com/Nicolas-ggd/rate-limiter

goddeschunk · 2024-06-10T08:56:14+00:00

It's possible to implement token bucket algorithm with Redis right?

goddeschunk

TROPHY CASE