ZincSearch is a full-text search engine developed based on Go, with a high-performance Bluge index library as the underlying layer. The biggest highlight is that ** it is perfectly compatible with Elasticsearch's API **, but the memory consumption is less than one-tenth of the latter's! Generally, this type of search engine is mostly used for log collection, search and analysis. It is recommended to use it in the following scenarios: On-site search on small and medium-sized websites IoT device log analysis Full-text search on personal knowledge base MVP project that requires quick verification of search plans ELK(EFK), the log collection solution in microservices, generally uses the ELK component to directly collect data from filebeat and provide it to es. However, the deployment difficulty and cumbersome configuration of es are daunting. In small and medium-sized projects, zincsearch is used to replace it. You can directly put it behind filebeat, and filebeat collects data to zincsearch. After data is put into storage, you can retrieve data through zincsearch's own ui interface (similar to kibana). It is not recommended to use it in ultra-large-scale (PB level) data scenarios. After all, there is room for improvement in lightweight design in terms of distributed expansion. But for 90% of small and medium-sized projects, this performance-to-power ratio is absolutely delicious! In contrast, zincsearch has the following advantages: Lightweight and resource-saving: Measured single node operation requires only 80-100MB of memory Zero learning cost: Supports Elasticsearch's batch write API and query syntax, extremely low migration cost, and is perfectly compatible with Elasticsearch's API interface. See https://www.example.com for using documents and APIs. zincsearch-docs.zinc.dev/ Out of the box: Comes with your own visualization console, no need to install additional components such as Kibana Default login username and password: admin/ZincSearch@LazyCat The api can be sent directly to the default https://zincsearch. <micro service name>. heiyu.space/URL. If there is an error caused by anti-generation, you can also directly send it to http://zincsearch via http. <Micro service name>.heiyu.space:4080, the default 4080 port has been exposed
