Zinc Search engine. A lightweight alternative to Elasticsearch written in Go

  • There are also Toshi[1] and Sonic[2] in Rust. And Vector[3] as a Logstash alternative too. There is an issue[4] proposing to integrate Vector with Sonic and Toshi. Maybe Zinc can pursue this goal too. Always good to see people who realize that Java is unwieldy monster that will eat all your memory. Native is a way to go for big systems.

    [1] https://github.com/toshi-search/Toshi

    [2] https://github.com/valeriansaliou/sonic

    [3] https://vector.dev/

    [4] https://github.com/vectordotdev/vector/issues/988

  • >(Kibana is not supported with zinc. Zinc provides its own UI).

    1. I was hoping for a drop-in replacement for Elasticsearch. A new/different API means Zinc can't leverage existing tools that use Elasticsearch.

    2. I don't like that you're bundling zinc with a UI; that disadvantages anyone else trying to build a better UI and often (usually?) leads to tying the db too closely to the UI (or vice versa)

  • Does it support boolean queries? Bluge, the library backing Zinc appears to have such a searcher, and I can see a few references in Zinc's code, but is it exposed for search expressions?

  • I am staunch supporter of software which runs on minimal hardware or resources. Seems like an interesting project, looking forward towards distributed features !

  • I wonder if this would be a good lightweight alternative to ES for a local development setup. At $work we use ES for deployed environments, but have thus far avoided running it locally because of the resource requirements.

  • Ha.

    Lovely, but the missing features is basically what makes Elasticsearch great!

        Missing features: 
        Clustering and High Availability
    
    Nothing that can't be fixed though.

  • When people say "Lightweight alternative" most of the time they are implying less features also, they are not lightweight just because

  • Would be nice to have some benchmarks against ES, Sonic, and Toshi. I am very much interested in stress-testing on large dataset.

  • I wonder why the choice of technology is even relevant? Because of the hype factor?

  • I've always wanted a full text search engine akin to "sqlite".

  • we have alternatives to elasticsearch as listed here. what we do not have is a alternative to kibana. which works with elasticsearch/opensearch and the elasticsearchalternatives here.

  • They had me at: "The only viable solution to search was elasticsearch".

    /s

  • there are already Bleve and Riot search engines written in Go. i am always happy to have more options but in this case maybe if the effort would have been put into one of these two would be overall more beneficial for end users.