Thank you. Honestly I did not known go-cache until now, so there might be more things to consider, but as far as I've sen, go-cache is key-value, while GEDB is document-driven, so there are some more querying features, like indexes and mongo-style filtering, sorting and projecting. Also, in README, go-cache mentions that it not meant to be persistent (even though it's possible), while my package was made to be persistent (you can use in-memory-only though). It was completely developed by me, no AI
This looks nice. I already use `github.com/patrickmn/go-cache`. Any difference between yours and go-cache? Also, how much of it has been ai developed?
Thank you. Honestly I did not known go-cache until now, so there might be more things to consider, but as far as I've sen, go-cache is key-value, while GEDB is document-driven, so there are some more querying features, like indexes and mongo-style filtering, sorting and projecting. Also, in README, go-cache mentions that it not meant to be persistent (even though it's possible), while my package was made to be persistent (you can use in-memory-only though). It was completely developed by me, no AI
Appreciate the reply. I've starred the repo and might give it a try in a future project