# spicedb


10/13/2022, 2:08 PM
Can you tell me more about your test? You likely want to be using the SpiceDB testserver
it creates an isolated in-memory datastore for each new token you use to talk to it
so there is no need to try to clean up your work on postgres


10/14/2022, 7:05 AM
Thanks I will check it out. In our tests we spin up the subset of our microservices that we test and populate them with a small amount of data to run our test against. Between tests the database is cleared as our microservices are stateless. Along we start spicedb and populate this with the permissions on testdata but also some initial permissions (think global rights and an initial admin user). So between tests we want to clear the permissions on testdata but not the initialization data. So we communicate directly to postgres to wipe the testdata permissions. But I was wondering, as spicedb has some caching mechanism (right?), does fiddling with the datastore directly hurt performance a lot?
The spicedb testserver looks interesting. When preloading data does this hold for every datastore in the token-isolation?


10/14/2022, 11:09 AM
Yes I believe so but I would have to double check.