What is the recommended architecture for running t...
# community-help
b
What is the recommended architecture for running typesense in production? Should we use postgres (or something similar) as primary datastore and sync the updates to typesense?
k
Yes, Typesense is not meant to be used as a primary datastore. Depending on how often your data changes you can do daily dumps or streaming updates.
b
Thanks!
What about security hardening? In a use case where there are multiple collections, multiple users, user1 should only have access to user1 documents, user2 only user2 documents etc. I'm thinking reverse proxy with nginx + SSL + scoped keys. Is there anything else that's recommended?
k
Scoped keys will handle user-level access control well. Nginx is optional because Typesense uses a production grade HTTP server library (h2o) which is used by Fastly in their edge deployments, so it's battle tested.
b
as a means to not expose typesense directly
k
It's fine to expose directly.
👍 1