this looks like an entirely AI built project from start to finish. there's 10 emoji filled commits and two obvisouly ai PRs. I think the description of the first commit reflects the prompt it was given:
- High-performance Redis-compatible cache with REST API
- 30-50% faster than Redis using Go's concurrency
- RESTful API with HTTP/JSON interface
- Pub/Sub messaging with WebSocket support
- Complex data types: String, List, Set, Hash
- Token-based authentication and security
- YAML-based configuration management
- Docker and Kubernetes support
- Comprehensive documentation and examples
- Postman collection and interactive web client
The brilliant author of this game changing key value store is also listed on his linked in profile as a frontend developer and has this brilliant little nugget to share in his latest post: "500 is an internal server error. It is very critical. It means something has exploded. If the client has encountered 500; "We are sorry to encounter this error. Please excuse us, we are interested."
But we see that; There are developers who use 500 even when giving validation messages.
You cannot take refuge in excuses such as time was limited or the budget was low. Typing 400 instead of 500 is not a very difficult thing!
Anyone who doesn't know where to use which status code is a teapot."
The “Lua engine” seems to support only one, hardcoded, command (redis.call) with no other syntax/lua operators! It even lacks conditionals! https://github.com/wutlu/boltcache/blob/main/lua.go
this looks like an entirely AI built project from start to finish. there's 10 emoji filled commits and two obvisouly ai PRs. I think the description of the first commit reflects the prompt it was given:
- High-performance Redis-compatible cache with REST API - 30-50% faster than Redis using Go's concurrency - RESTful API with HTTP/JSON interface - Pub/Sub messaging with WebSocket support - Complex data types: String, List, Set, Hash - Token-based authentication and security - YAML-based configuration management - Docker and Kubernetes support - Comprehensive documentation and examples - Postman collection and interactive web client
The brilliant author of this game changing key value store is also listed on his linked in profile as a frontend developer and has this brilliant little nugget to share in his latest post: "500 is an internal server error. It is very critical. It means something has exploded. If the client has encountered 500; "We are sorry to encounter this error. Please excuse us, we are interested."
But we see that; There are developers who use 500 even when giving validation messages.
You cannot take refuge in excuses such as time was limited or the budget was low. Typing 400 instead of 500 is not a very difficult thing!
Anyone who doesn't know where to use which status code is a teapot."
Lots of bold claims for something with a single release straight to v1...
I'd be curious how this compares to NATS, most of all. Or even etcd
Hey, nice project, but I'm wondering if I'm just missing any _test.go files, or if there are none ?
Especially for the performance claims these or a Readme on how to replicate them would be great.
> High Performance: 30-50% faster than Redis using Go's concurrency
Where is the benchmark script? I would like to see the scenario, client used and machine config.
Don't take me wrong but from just skimming over the readme I can't believe the numbers.
the entire benchmark part of the readme was added by an ai bot last week in a random swagger PR ? :D https://github.com/wutlu/boltcache/pull/1/files#diff-b335630...
There were some statistics in the readme, but didnt see the testscript
> with better performance
Based on what exactly?
Looking at the feature list, what doesn’t it do?