https://authzed.com logo
#spicedb
Title
# spicedb
w

williamdclt

03/03/2022, 9:45 PM
Given that SpiceDB relies a lot on in-memory caching for performance, how do you handle updates to the service? Eg when
v1.4.1
comes out, I'll want to roll it out: it will mean a new set of pods replacing the
v1.4.0
ones (we use k8s) and therefore losing all the cache and probably seeing huge response time spikes. Is it "simply" a matter of making it a slow rolling update? How slow?