Sure thing, we’re experimenting with some Load-Balancing heuristics and instrumentations, and it looks it got rate-limited by the engine who got surprised all traffic was coming from a single IP /o\
Let’s say it was a mix of HN alerting (hnwatcher), good timing (Friday evening) and luck :) very happy to have seen this in time. Have a nice WE as well!
[HN Search admin speaking] We disabled the rate-limit for now. A load-balancer experimentation that didn't behave as expected (the LB's IP getting rate-limited).
Btw, part of this pricing rework is also about removing some of the feature gating. It's an approach we've taken to really get the feature right, first releasing it to a smaller set of (larger) customers before opening it up to the whole mass.
(Sylvain from Algolia speaking) Thanks for sharing, our pricing & its transparency is actually something we are working on right now to address this perception. We've been iterating a few times already over the past 7 years, but this is one more signal for us to act!
The reality is that based on the number of objects you want to search in, your search traffic, your searches' complexity and your index/relevance configuration; the underlying resources can vary soo much, it's hard to have a single pricing that fits all use-case.
Yes, when sorting by date it's currently configured to disable typo-tolerance. This is to avoid having an old (but approximative, with typos) result BEFORE the correct ones.
You should give it a try; Algolia has a FREE tier you can play with. You can also watch this 45sec video to get a grasp of it: https://youtu.be/IYY5RM1sBC0
Yes, when sorting by date it's currently configured to disable typo-tolerance. This is to avoid having an old (but approximative, like with typos) result BEFORE the correct ones.