Understanding Alias Usage in API Collections and Environment Security
TLDR gab sought clarity on when collection aliases would be used, if they are public and how they handle different environments. Kishore Nallan explained their purpose and suggested using distinct API keys for each environment for privacy and customization. They also directed gab on how to generate these keys per collection.
Jul 30, 2021 (28 months ago)
gab
12:18 PMIn which cases an alias of a collection will be used ? It is something used only when we use search queries or it is also used for any other api?
Kishore Nallan
12:20 PMgab
12:38 PMgab
12:43 PMKishore Nallan
12:47 PMbooks and then everyday you create a new collection, say books_30_JUL_2021, index it and then just update the books alias to point to this new collection.Kishore Nallan
12:47 PMgab
12:56 PMBut I thought the effective collection name wouldn't have been exposed to the search api.
Let's say I have
product alias to product-Whatever . And then I perform a search using only the search token. I wouldn't know about the existence of product-whateverKishore Nallan
12:59 PMgab
01:12 PM`${name}-${environnement}-${date}`With the alias I can then point wherever I want.
My front application always ask for the alias.
My backend layer create collection & appropriate alias dependending on the environnement.
But the environnement is not something I would like to expose publicly. Nor the date.
For now I can just compose the collection name without "readable information"
Kishore Nallan
01:14 PMgab
01:24 PMI started on typesense cloud with one cluster per environnement. So I had different api keys.
The issue was it cost me Runtime cpu on each cluster even if the environnement was not used at all.
So I have put everything on the same cluster so if at least one env is used, the cluster is not running for nothing.
๐ would have prefered to completely have separated envorinnements
Kishore Nallan
01:36 PMgab
01:40 PMKishore Nallan
01:40 PM
Typesense
Indexed 2786 threads (79% resolved)
Similar Threads
Resolving Issues with Scoped API Keys in Typesense with Golang
Suvarna had problems with generating and using scoped API keys in Typesense with Golang. Several bugs misleading the user were found and fixed by Kishore Nallan.
Authorization Issues and Version Update Queries
gab was having authorization issues with multisearch but Jason advised using the collection name instead of the alias when creating the key. gab also queried about updating the cloud cluster to a later version.
Discussions on Typesense, Collections, and Dynamic Fields
Tugay shares plans to use Typesense for their SaaS platform and asks about collection sizes and sharding. Jason clarifies Typesense's capabilities and shares a beta feature. They discuss using unique collections per customer and new improvements. Kishore Nallan and Gabe comment on threading and data protection respectively.
Comparing Performance and Security of Different Data Collection Methods
bnfd asked about differences in performance and memory usage between a single, large data collection and multiple smaller collections. Kishore Nallan explained that the latter is faster, suggested 100 collections sharded by user_id, and informed about the use and security of scoped API keys.
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.