HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
toshi-search
Toshi
Rust2018–2024
toshi-search / Toshi

Toshi

A full-text search engine in rust

14Distinct people
25Mentions
0Explicit recommenders
4.3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A full-text search engine in rust

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 2:19:09 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year25 dated mentions

Observed mentions: 2018-12-28 14:06:07 UTC to 2024-10-14 15:35:49 UTC.

0369122018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 12 mentions; 1 submissions, 11 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC101
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC12111
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC505
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC505
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101

What Hacker News says

12 sources
It would be nice to integrate all Rust alternatives to ELK stack: 1. Toshi[1] - alternative to Elasticsearch 2. Sonic[2] - alternative to Elasticsearch 3. Vector[3][4] - alternative to Logstash 4. native_spark[5] - alternative to Apache Spark [1] https://github.com/toshi-search/Toshi [2] https://github.com/valeriansaliou/sonic [3] https://vector.dev/ [4] https://github.com/timberio/vector [5] https://github.com/rajasekarv/native_spark
In Bayard: a full-text search and indexing server written in Rust
Elasticsearch is very popular because it works well for generic searching and can be customized for lots of unique scenarios. There's competition on the infrastructure side using something other than Java/JVM though: For Rust, there's Toshi: https://github.com/toshi-search/Toshi which is built on top of Tantivy: https://github.com/tantivy-search/tantivy For C++, there's Xapiland: https://github.com/Kronuz/Xapiand For Go, there's Blast: https://github.com/mosuka/blast built on Bleve: https://github.com/blevesearch/bleve
In Ask HN: Are Lucene/Solr/ES Still Used for Search?
Porting unique and omnipresent applications to Rust can help the adoption. For example applications like ElasticSearch. There is an ongoing Toshi[1] project to create an alternative. Creating analogs for IPython and LanguageTool can add much more Rust users and developers without significant promotional efforts. [1] https://github.com/toshi-search/Toshi
In Rust's 2019 Roadmap
Always nice to see more alternatives to Elasticsearch. That project could be so much better with some proper planning and focus. There's also Toshi: https://github.com/toshi-search/Toshi which is built on top of Tantivy: https://github.com/tantivy-search/tantivy And for C++, there's Xapiland: https://github.com/Kronuz/Xapiand And for Go, there's Blast: https://github.com/mosuka/blast built on Bleve: https://github.com/blevesearch/bleve
In Sonic: Fast, lightweight and schemaless search back end in Rust
This looks interesting. I agree with your point that there is huge gap between engineers and stakeholders. And a lack of understanding on how value is created and how it is attributed. I would like to understand how source level metrics can help me better understand my own contributions to the project. Do you have some examples/stores where you used the matrices in your team to understand the contributions? Also a comment about about ELK. I recently found this full text search project called Toshi: https://github.com/toshi-search/Toshi . It is written in Rust and provides (almost) same functionalities as ES. But is less heavy than ES and probably easy to deploy. Do you have any thoughts on it?
In Show HN: Visualize Git Commits and Pull Requests Across Many Repos

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.