I’m implementing Badger in my app to be used as a global cache store. It fits the purpose but because I have a quite a number of jobs running at the same time, I use prefixes to partition the database for specific jobs.
The concern I have is that each job is identified by a UUID (16 bytes) then an additional, say, 8 bytes to indicate what the key refers to (ie. maybe a timestamp or such). Would this be too long to be used as a key? Is there any performance concerns I should be worried about? I’m most worried that if the key is too long, it may cause it to be escaped to the heap.