Multi-region TS SDN and Data Center Locations Query
TLDR Campbell asked for recommended data centers for most search volume and if they could use their own subdomain. Jason suggested Ohio, Frankfurt, Sydney, Singapore, São Paulo, and using Cloudflare DNS.
Jun 29, 2023 (5 months ago)
1. Our primary search volume will come from Europe/UK, US/CA, and Australia. Do you have any recommendation for the specific data center locations we choose in each of those 3 regions?
2. Can we use our own subdomain for the cluster, either A or CNAME to reference it?
As a nice side-benefit you also get DDoS protection: https://typesense.org/docs/guide/data-access-control.html#ddos-protection
Jul 07, 2023 (5 months ago)
Indexed 3015 threads (79% resolved)
Troubleshooting Typesense Cluster Sync Issues in K8s Environment
Robert encountered node syncing issues in the K8s cluster with Typesense nodes. Kishore Nallan offered advice, including using DNS names and suggesting a call. Robert plans to use a single region Typesense with Redis caching. The thread resolved with the possibility of configuring Typesense with DNS names from 0.21.0.
Optimizing Typesense Implementation for Large Collections
Oskar faced performance issues with his document collection in Typesense due to filter additions. Jason suggested trying a newer Typesense build and potentially partitioning the data into country-wise collections. They also discussed reducing network latency with CDN solutions.
Protecting Typesense Queries from DOS Attacks
Juri sought advice on securing typesense queries. Jason suggested use of Cloudflare for DOS attack protection and explained how to create user-specific API keys for data authorization. Ricardo endorsed Cloudflare for protection.