Fail-open: why your site never “breaks” because of search
An external service should never bring your shop down. See how Findora quietly steps aside if something goes wrong.
Every service you add to your shop is also a potential point of failure. What happens if the search service doesn’t respond? With many solutions the answer is uncomfortable: a broken search box, a page that “hangs”, customers who leave.
Findora was designed around the opposite rule: never a broken site.
If Findora doesn’t respond in time, the shop’s search works as it always has.
How it works
- 800 ms time limit: if Findora doesn’t respond within this window, the script doesn’t intervene. The shop’s search form submits to its own results page, just as it did before Findora.
- Asynchronous loading: the script loads without delaying the rest of the page. If it doesn’t load at all, the site doesn’t notice.
- No JavaScript errors: every failure is caught internally and is never shown to the customer.
- Same behaviour when a subscription ends: if a subscription expires or a payment fails, after the grace period the shop reverts to its own search. An error page is never shown.
And behind it all
The service runs on servers in the European Union, behind Cloudflare for protection against attacks and bots, with per-shop request limits so that a shop with excessive traffic doesn’t affect the others.
Updates without interruption
Every improvement to the service is rolled out without search stopping. Two copies of the service run side by side: while one is being updated, the other responds, and traffic switches to the new one only once it is ready. In a test with continuous requests during an update, every request was answered, without a single error. Service status will be published at status.findora.tech.
Want to see how it would work with your own catalogue? Request a demo.