jlemoine

9 ms·

31.
by jlemoine 9y ago
I am sad to see you had a bad experience with Algolia and I can assure you that we put a lot of effort on backward compatibility: * we have never discontinued a feature in the API since the launch * We never broke our API clients, we propos
32.
by jlemoine 9y ago
For testing, we propose free accounts. For the different sort, we did the choice to emphasis quality over cost, on purpose :) In practice, it means we need to duplicate the data for each sort in order to do has much as possible at indexing
33.
by jlemoine 9y ago
(CTO of Algolia here) We have just the right to host the service for you on your data, it remains of course your property!
34.
by jlemoine 10y ago
We were using CloudFront at the beginning but we had a lot of performance problems to deploy our binaries worldwide (especially in Africa and Russia). We have seen a big performance improvement by switching to Cloudflare that have a POP in
35.
by jlemoine 10y ago
You're right that low DNS TTL is not perfect (we saw few providers that override the TTL to reduce the number of DNS queries going out of their network, this is a big hack but cause some trouble). This problem is addressed by our API c
36.
Comparing Algolia and Elasticsearch for Consumer-Grade Search Part 1(blog.algolia.com)
7 points by jlemoine 10y ago|0 comments
37.
Algolia Is Hiring Solutions Engineers in SF, NYC, Paris, London and Sydney(algolia.com)
1 points by jlemoine 10y ago
38.
Inside the Algolia Search Engine Part 6 – Handling Synonyms the Right Way(blog.algolia.com)
5 points by jlemoine 10y ago|0 comments
39.
For SLAs, there’s no such thing as 100% Uptime – only 100% Transparency(blog.algolia.com)
3 points by jlemoine 10y ago|0 comments
40.
by jlemoine 10y ago
I would recommend to read this post to have an idea: https://blog.algolia.com/inside-the-algolia-engine-part-3-qu... Textual relevance is a very complex domain and the Postgres's built in text search features is a simp
41.
by jlemoine 10y ago
We actually have pretty complex implementation done with Algolia. Like a grocery store where relevance depends of the history of each user. As with any engine, there is a lot of customization possible to handle complex use cases and it won&
42.
by jlemoine 10y ago
This result is indeed not good but it could be solved easily with one Algolia setting (removeWordsIfNoResult=allOptional which perform the query with all terms as mandatory and reply it with optional terms if there is no result). Algolia co
43.
by jlemoine 10y ago
Algolia contains a lot of customization parameters that can be used. For example the Product Hunt example could have been solve easily by using removeWordsIfNoResults=allOptional (query is trying as a AND and if there is no results, it is t
44.
Tech Due Diligence Calculator for Startups(medium.com)
1 points by jlemoine 10y ago|0 comments
45.
Algolia (YC W14) is hiring engineers, sales, marketers(algolia.com)
1 points by jlemoine 11y ago
46.
Algolia (YC W14) is hiring engineers, sales, marketers(algolia.com)
1 points by jlemoine 11y ago
47.
Algolia’s Checklist for Selecting a Critical SaaS Service(blog.algolia.com)
1 points by jlemoine 11y ago|0 comments
48.
Best practices for documentation search(blog.algolia.com)
1 points by jlemoine 11y ago|0 comments
49.
Algolia (YC W14) is hiring a senior Rails engineer(algolia.com)
1 points by jlemoine 11y ago
50.
How to build a good search in your tech documentation(blog.algolia.com)
1 points by jlemoine 11y ago|0 comments
51.
Algolia is hiring 20 persons in the next 2 months(algolia.com)
1 points by jlemoine 11y ago
52.
by jlemoine 11y ago
Have you tried the "Custom range" filter option to select a range of date?
53.
Algolia search API is now available in 13 regions / 25 datacenters(blog.algolia.com)
1 points by jlemoine 11y ago|0 comments
54.
Algolia (YC W14) Is Hiring Product Marketing Experts(algolia.com)
1 points by jlemoine 11y ago
55.
Algolia (YC W14) Is Hiring Customer Success Engineers(algolia.com)
1 points by jlemoine 11y ago
56.
Algolia raises a $18.3M Series A(techcrunch.com)
18 points by jlemoine 11y ago|1 comments
57.
How we are using DNS fallback in our API clients for better resilience(blog.algolia.com)
2 points by jlemoine 11y ago|0 comments
58.
How we have implemented and tested our isomorphic JavaScript API Client(blog.algolia.com)
8 points by jlemoine 11y ago|0 comments
59.
Don’t let network latency ruin the search experience of your end-users(blog.algolia.com)
1 points by jlemoine 12y ago|0 comments
60.
8 Tools to Make Your MVP Look Like a Pro Product(blog.venturepact.com)
3 points by jlemoine 12y ago|1 comments

More ›