Rate Limit Issues for APIs on Typesense Cloud
TLDR Zildjian reports a rate limit issue but Kishore Nallan claims Typesense doesn't enforce rate limits. The issue seems associated with server-side API calls from nextjs.
Sep 05, 2023 (3 weeks ago)
Zildjian
07:54 AMKishore Nallan
07:55 AMZildjian
07:56 AMAxiosError: Request failed with status code 429
Zildjian
08:03 AMKishore Nallan
08:04 AMZildjian
08:04 AMKishore Nallan
08:05 AMZildjian
08:07 AMKishore Nallan
08:23 AMZildjian
08:26 AMKishore Nallan
08:28 AMZildjian
08:28 AMKishore Nallan
08:28 AMZildjian
08:29 AMZildjian
08:29 AMKishore Nallan
08:30 AMTypesense
Indexed 2779 threads (79% resolved)
Similar Threads
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.
Importing data to Typesense Cloud with JS client
Zaiste attempted to import data to Typesense Cloud but encountered an error. Kishore Nallan explained the error was due to server side backpressure and suggested a curl approach for the import.
Rate Limiting for Self-Hosted Typesense
David asked about rate limiting on self-hosted Typesense. Jason recommended using Cloudflare until Typesense introduces rate limiting.
Discussing Features for Typesense Cloud Dashboard
Stephano expressed the need for a Typesense Cloud dashboard to manage collections. Jason confirmed its development, also including features like editing and deleting items. James and Mica added comments about API key management and self-hosted Typesense compatibility.
Debugging Typesense API Key Error
James is getting an error related to the `x-typesense-api-key` header in their Typesense project. Harrison suggests passing the API key in the HTTP header, and Jason advises checking the key via curl and possibly closing a duplicate Typesense server.