I'm a backend-focused software engineer with deep experience building scalable, cloud-native systems. I’ve worked with startups across Latin America, Europe, and the U.S., taking on roles that span backend development, cloud infrastructure, and DevOps. My main area of expetise within backend is database tunning / optimization.
It’s not feasible to do that in a single threaded system.
The main drawback of disk persistence is that you need a log of memory to keep the file buffer open and pointers.
If the key you’re looking for is not on disk, you’ll get awful results, the rdb format will give you worst then Postgres performance. You have to use another file format to optimize for a larger cache
Agree. I used it mostly for getting ideas, the memory management for example, Gemini listed so many different ways of managing memory I didn’t even know existed.
I know I wanted to pre allocate memory like tigerbeetle does, so the hybrid approach was perfect. Essentially it has 3 different allocators, a huge one for the cache, a arena allocator for context, intermediate state like pub/sub and temp one, for requests.
It was 100% Gemini’s idea.