Show HN: GEDB – A pure-Go embedded database
4 comments
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
[deleted]
These last few months I've been working on my first open source project: an embedded database written in pure-go. That took me some months, as I had to learn how to deal with such large packages. Until then, all packages I had made were quite small an did not require much. I usually did not have to worry about things like allocation optimization and instance pools until This project.
It started when I wanted to make a port of a tool to a TUI environment. I'm actually used to working with TUIs in golang, so that was my language of choice. The tool I wanted to port is written in TypeScript and uses NeDB (written in JavaScript) as database. Since I feel more comfortable working with compiled languages, I decided to create my own database, making sure it was compatible with NeDB, and that's what I did for the last few months.
And that's how GEDB was created. It's a mongodb-like embedded database, written in pure-go. It supports a subset of useful querying options of MongoDB (keywords like $lt, $exists, $in, $where, etc.). By default, it uses a in-memory-only storage, but can easily initialized with a data file.
Everything in my package can be dependency injected, as everything is controlled interfaces. Serialization, querying syntax, document structure, indexing and more, all can be replaced by implementing an interface.
I've also been considering adopting a new document model, by creating a binary type (like BSON) to reduce drastically the cost of creating, maintaining and copying documents (they currently are map[string]any).
The project is currently in an early stage, version 0.1.0, so I'm okay with making changes to the API for now, until I'm ready to release version 1.x.x
I would be really glad if you guys could check it out and give some feedback. An issue, suggestion or a star are very welcome.
My repository can be found on my github: https://github.com/vinicius-lino-figueiredo/gedb