3 ms·
I'm new to search libraries (frameworks?) but have been looking for something to use for a huge data dump I'm working with. Storing everything in memory seems
by drusepth 7y ago
I'm new to search libraries (frameworks?) but have been looking for something to use for a huge data dump I'm working with.
Storing everything in memory seems fast, but seems like it'd be quite the resource hog on a server -- is that a normal approach to take?
It's reassuring that the examples and documentation all revolve around books (as my data set is actually ~55 million books also), but since theirs seems to be quite the subset of that I worry about how well this scales and I don't know enough about search libs to even evaluate that.
Is there a good place to start learning about what kinds of situations Typesense works best in (besides needing a Levenshtein-based search), versus what kinds of situations it wouldn't work well in (and perhaps what other libraries would work better)?
- karterk 7y agoTypesense'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 and the benefits from a solid search user experience. Other libraries like Elastic offer more customization but also has a steeper learning curve.