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
Kishore Nallan
08/25/2021, 2:55 PM
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
bnfd
08/25/2021, 3:05 PM
Thanks!
bnfd
08/25/2021, 3:08 PM
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
Kishore Nallan
08/25/2021, 3:09 PM
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.