Howdy! I'm working on a rebuild of a multitenant SaaS product that helps non-profits and associations manage their memberships. So things like groups, dues, calendar events etc. SpiceDB looks .... awesome. I have two main questions: 1. Do people typically use a message broker to manage updating SpiceDB in response to certain events? I'm looking hard at NATS and/or Watermill 2. How is multitenancy typically handled? If I want each tenant to have control over their policies, would each tenant need their own instance?

Hi 👋 1. Updating SpiceDB via Event Streaming is pretty common. We have customers doing so (e.g. Kafka) 2. If each tenant has a different SpiceDB schema, then yes you need multiple SpiceDB clusters. You can do that fairly easily using the spicedb-operator for Kubernetes. However, I suspect that may not be what you want, the schemas are rarely defined by the tenant themselves. What you usually define is a schema that allows you to express all your business domain. And in that case it would be easy to run a multi-tenant service with a single instance.

Thank you! I'm learning a ton about it this morning

Anytime!