karterk

17 ms·

121.
by karterk 6y ago
If you're looking to do the same on something that's easier to run and manage than ES, consider using Typesense: https://github.com/typesense/typesense The primary benefits are simplicity, typo tolerance and
122.
by karterk 7y ago
Since so many people are sharing their story, I will share mine. 5-6 years ago, I started working on Typesense ( https://github.com/typesense/typesense ), an open source, typo tolerant search engine designed for speed an
123.
by karterk 7y ago
If you are looking for alternatives, check out Typesense as well: https://github.com/typesense/typesense It supports multiple filters and has HA for reads as well.
124.
by karterk 7y ago
If you are looking for alternatives, check out Typesense as well: https://github.com/typesense/typesense
125.
by karterk 7y ago
Thanks, this has been fixed.
126.
by karterk 7y ago
Typesense does support faceted search. Look for the `facet_by` example in this section: https://typesense.org/docs/0.11.1/api/#search-collection
127.
by karterk 7y ago
> Typesense use a default_sorting_field on each document, it means that before indexing your documents you need to compute a relevancy score for typesense to be able to sort them based on your needs This is not entirely true. You can jus
128.
by karterk 7y ago
I agree with everything you've said. I was a bit sloppy in not mentioning the trade-offs. My "fast enough" remark was certainly not for handling large datasets. The parent comment had asked why Lucene was not used for Typ
129.
by karterk 7y ago
Definitely going to work on that.
130.
by karterk 7y ago
Likely an integration with an existing popular UI search library.
131.
by karterk 7y ago
We support English and other European languages (supports fuzzy search normalizing accented chars). While it does not support stemming, with fuzzy prefix matching, it will largely work and practically more useful. No typo or fuzzy correctio
132.
by karterk 7y ago
Typesense's primary focus is speed and developer convenience. It makes an assumption (which is true for perhaps 99% of the time) that memory is cheap enough for indexing most datasets. Especially given the effort of development time an
133.
by karterk 7y ago
Yes, for typo correction + instant search, Lucene definitely is not fast enough on large datasets. There are also some limitations with fuzzy searching when you also want to sort/rank documents at the same time. Lucene is also a very g
134.
Typesense: Open-Source Alternative to Algolia(github.com)
447 points by karterk 7y ago|54 comments
135.
by karterk 7y ago
This essentially comes down to quantity vs quality. Keyword research, link building etc. helps you optimize for your time. You can achieve the same traffic from fewer posts. Otherwise you have to keep churning out posts and make up for it i
136.
by karterk 7y ago
This is a topic that I have been thinking a lot on recently. I've been working on a typo-tolerant instant search engine for a couple of years now called Typesense ( https://github.com/typesense/typesense ). It has n
137.
by karterk 7y ago
Elasticseach is notoriously hard to roll out and develop against (for smaller companies especially), and so I am happy to see smaller projects in this space. I've also been working on a light, fast, typo-tolerant search engine: https:
138.
by karterk 7y ago
Back when I was in college, someone gifted me Randy Pausch's "The Last Lecture". It was my first introduction to this terrible disease. Little did I know then, that a decade later, I would lose my beloved father in-law to the
139.
by karterk 7y ago
raises hands Most of my early carrier involved PHP, JavaScript and Python. I started appreciating type systems only when I began working on larger code bases. Types might slow you down initially but I personally find it very comforting t
140.
by karterk 7y ago
India has been conducting elections via electronic voting machines for a while now: https://en.wikipedia.org/wiki/Electronic_voting_in_India In India's case, the paper ballots actually caused a lot of rigging as b
141.
by karterk 7y ago
This was exactly my pain point as well. For smaller projects, ES is a overkill. So I decided to do something about it! I started working on an open source, really, developer friendly search engine that just works. It's pretty stable no
142.
by karterk 7y ago
Yes! Please take a look at an open source search engine I am working on. You will definitely like it: https://github.com/typesense/typesense Would love to hear your feedback :)
143.
by karterk 7y ago
I have been working on an open source alternative: https://github.com/typesense/typesense Would love to hear your feedback :)
144.
by karterk 7y ago
The trie is my favorite data structure. It allows you to build inverted indices (i.e. hashmaps) that can also be used for prefix lookups of tokens and for spelling/typo correction. With a trie, it's very efficient to calculate Lev
145.
by karterk 7y ago
5 years ago, I had a crazy idea that there must be an open source engine that had a really simple learning curve and worked out of the box. The result: https://github.com/typesense/typesense It took me over 3 years to
146.
by karterk 7y ago
I was merely highlighting the convenience of a HTTP based RESTish API. It will be a familiar pattern instead of a custom text based protocol over tcp.
147.
by karterk 7y ago
Looks like the project is still under development but I think that having a http based interface would make this much more accessible to be used easily from multiple languages. Disclosure: I work on a similar open source search engine ( htt
148.
by karterk 7y ago
There were very few ready-made frameworks and libraries to get things done, so it was fun writing those meta libraries that runs your business. Of course, purely from a business point of view, this is not ideal and is extremely wasteful. At
149.
by karterk 7y ago
I've been working on an open source search engine ( https://github.com/typesense/typesense ) and this exact deliberation has been on my mind. Ideally, one could offer both on-premise and hosted versions (like Gitlab
150.
by karterk 7y ago
Most people (regardless of where they are in the world) are not going to be able to afford a cluster of any meaningful size. So, the best option is to learn these tools by running them on your local machine. You can use Virtualbox or Docker

More ›