What is the crowd's opinion of Typesense?

From 3.5 billion comments

Hi all; I designed a site called Iconduck (iconduck.com).

There are so many dope open source icon sets out there. I brought a bunch of them (132 so far) under one roof. I made them searchable (using typesense.org), and list out the license details and link back to the site or GitHub repo.

I'm not much of a designer, and it's just a first stab at the concept. It's been done, but I wanted to also build it API-first, since I know it would be useful to be able to search through them all for developers.

I'm always on the lookout for new icon libraries to include, and plan on making it easier to learn more about the designers themselves. If you have any ideas on icon sets or libraries to include please let me know in the comments :)

Not sure if this will help but I read this yesterday and it really helped me calm down and continue working on my side hustle. https://typesense.org/blog/the-unreasonable-effectiveness-of-just-showing-up-everyday/

In this case, that is what it means; and it appears to use Levenshtein.

1. Tener una idea CERRADA/FINITA de lo que quieres. Cuanto más específicada tengas la idea, más facil será implementarla.
2. Dividir las tareas en cosas pequeñas, abarcables
3. Crear una disciplina de trabajo. No dejar nada en manos de la motivación o no acabarás nada:
   • The unreasonable effectivenes of just showing up everyday
   • Most people overestimate what they can do in one year but underestimate what they can do in ten. -Bill Gates
4. Tira palante, hay que publiar algo, aunque creas que esté mal. Una vez publicado ya tendrás tiempo de arreglarlo. Nada sale bien a la primera.

Thank you for mentioning Typesense u/JuriJurka!

Hi u/samtstern, I'm one of the founders of Typesense. We've been seeing increased interest in Typesense from Firebase users recently. Algolia is a fantastic product with a great developer experience like you mentioned, but it can quickly get expensive for even moderate scale use-cases - I've heard this countless times from people now.

The other well-known alternative is to then resort to using ElasticSearch, which is a powerful and flexible search engine, but it also brings with it a steep learning curve and added operational overhead. Compared to Algolia, the DevX with ElasticSearch is not the best, from my own personal experiences and from what I've heard from users, since it's a complex piece of software.

With Typesense, we're building an open source search engine that gives developers the same intuitive DevX and instant-search performance that Algolia offers, while minimizing the learning curve and operational overhead that ElasticSearch brings with it. Cost-wise, users can choose to self-host Typesense for free or in the case of Firebase users who might prefer hosted services, they can opt to use Typesense Cloud, which is a fraction of the price compared to Algolia.

I've been eyeing this page on the Firebase documentation for a while now! Would be great to have Typesense included as another option on that page. The integration with Typesense is almost identical to the integration with Algolia.

Open to any other ideas as well!

THANKS A LOT!!! ❤️😭❤️😭❤️😭❤️Typesense is really awesome, and the DevX is really at the same level as Algolia because they have now their own Typesense Cloud. It's extremely easy to use with nearly no code at all, it's very great for beginners and starters. + they have awesome customer service for everyone. You can just ask your questions in the slack and they immediately respond back with help

https://www.reddit.com/r/Firebase/comments/na8hqu/full_text_search_if_you_hate_algolia_for_pricing/?utm_source=share&utm_medium=ios_app&utm_name=iossmf Please take a look at this post. The typesense founder himself explains the key difference between algolia and typesense.

here is another Comparison

https://typesense.org/typesense-vs-algolia-vs-elasticsearch-vs-meilisearch/

The results are indeed based on the text in the comics as well.

I was initially thinking of doing OCR , but thankfully explainxkcd has already done this important work, so I was able to get the transcripts from there and index them.

Here's a feature-by-feature comparison between Typesense, Algolia, ElasticSearch and Meilisearch: https://typesense.org/typesense-vs-algolia-vs-elasticsearch-vs-meilisearch/

Here's another text blurb: https://typesense.org/docs/overview/comparison-with-alternatives.html#typesense-vs-meilisearch

Thank you for the feedback. May I know which part of the installation guide didn't work as expected? I'd love to address any confusion and improve the docs.

Super projet ! Je pense qu'un typesense pourrait être une bonne addition au site. C'est un bon cas d'usage je pense, pour trouver rapidement toutes les déclarations qui nous intéressent ! Dispo pour en parler si besoin :)

Depending on number of records, Algolia can get pretty expensive. There’s also Typesense, which is an open source alternative to Algolia: https://typesense.org/docs/0.21.0/guide/dynamodb-full-text-search.html

You can certainly use ElasticSearch to search by particular fields in a document, but running ES in production is quite complex.

Typesense is another way to do this, and has a much simpler intuitive API. There’s also a guide on how to integrate DynamoDB with Typesense here: https://typesense.org/docs/0.21.0/guide/dynamodb-full-text-search.html

Typesense was around before Meilisearch. So technically, the question is, doesn’t Typesense already do the trick :)

Here’s a feature-by-feature comparison between Typesense, Meilisearch, ElasticSearch and Algolia: https://typesense.org/typesense-vs-algolia-vs-elasticsearch-vs-meilisearch/

Hi all :)

It's called Iconduck (iconduck.com).

There are so many dope open source icon sets out there. I brought a bunch of them (132 sets so far; just over 100k icons) under one roof. I made them searchable (using typesense.org), and list out the license details and link back to the site or GitHub repo.

I'm not much of a designer, and it's just a first stab at the concept. It's been done, but I wanted to also build it API-first, since I know it would be useful to be able to search through them all for developers.

Appreciate any design feedback and/or ideas :)

I've been thinking about doing a project with music albums from Wikidata, and I was not looking forward to the search piece. But the guide makes things look pretty straightforward, might have to try this.

I'd probably reach for Elasticsearch too, but there are a few other options if that's not viable.

I stumbled across Typesense, which sounds quite interesting, but haven't used it.