i am very new to pinot, but have some high level q...
# getting-started
l
i am very new to pinot, but have some high level questions and am happy to RTFM if they are answered somewhere and this is the wrong place to ask them; for example, is pinot suitable for use in high volume read situations? for example, if i have many REST or graphql services hitting it for a several thousand users, is that an appropriate use for it, or am i "holding it wrong"?
k
Short answer is Yes. However, it will require careful data modeling, partitioning of data , using the right segment assignment strategy and indexing techniques.
๐Ÿ‘ 1
l
thanks
i was not assuming it would be a magic bullet (i have seen too many of those fail to know better), but i was more wondering if it was suitable for a large number of connections executing a lot of queries concurrently. but as i think on it more, i wonder if pinot should be more of a "secondary" data store in my scenario, and some sort of memory-based cache should be used in a more targeted way to handle the most common requests, leaving pinot as the "oops we missed this case, just query it..." option
but it sounds like either could work if we are diligent at learning how to use it well
m
There are deployments where Pinot is serving 200k queries / second (20k for one of the tables), without any cache. Unless your queries are super expensive, you donโ€™t need cache. Happy to help in optimizing the latency and throughput once you get there
l
nice, thanks! this is exactly the kind of information i was looking for ๐Ÿ˜„
๐Ÿ‘ 1