Anish Mukherjee

@hiqsociety yes actually, the current implementation of goroutines (go 1.18) is such that using unlimited goroutines is faster than using a goroutine pool at the cost of extra memory here...

The logs and reloading for redis databases have to be handled differently because for redis a new container is created per user database which is different from other database services...

Implementation of raft + badgerDB consensus https://yusufs.medium.com/creating-distributed-kv-database-by-implementing-raft-consensus-using-golang-d0884eef2e28

Raft -> https://raft.github.io/ BadgerDB -> https://github.com/dgraph-io/badger

@karan0299 what will this exactly do? We are already backing up the databases by mounting the volumes i.e `mysql-storage` and `mongodb-storage`

this could be useful if we were to make an admin panel for monitoring the entire ecosystem In that panel, we can also view the logs of all instances Probably...

moved to https://github.com/sdslabs/gasper/issues/205

@vrongmeal done

The queue length is fixed and provided by the user during the initialization of zenq such as `zenq.New[int](32)` The default queue size is 4096

> Why there is padding at the beggining of ZenQ structure? Simple reason would be the benchmarks ran faster with padding on top on 2 of my systems. I don't...