jina VS Weaviate

Jina mainly because of their use of neural networks and AI.

Jina - It’s an open-source project where you can build search engines. Well maybe not no code but it claims that you only need a few lines of code for creating projects. The project supports semantic, text, image, audio, and video search. What I’m also interested in is with their neural search and generative AI. I’m also interested in the amount of github repo that they have. I have this on my radar since this is also something I was interested in.

Do you guys have any ideas how we can match images on our database? We’re working on a project that about matching images on our database. We were trying to use SIFT and some other similar methods, but for some reason, nothing doesn’t seem to be working that well. Does anyone have any suggestions for the most effective way to do this? Maybe some open-source solutions like HuggingFace or Jina AI? We just want to make sure our image matching is correct and that part’s been a bit of a struggle on our part.

The tech lets you find 3D models without sifting through tons of text - An information retrieval framework does the heavy lifting and compares models to each other, no descriptions or keywords needed.

Jina AI -They offer a neural search solution that can help build smarter, more efficient search engines. They also have a list of cool github repos that you can check out. Similar to Vertex AI, they have image classification tools, NLPs, fine tuners etc.

Well, it's not exactly a new feature, but we've been working on early support for DocArray v2 in Jina.

Jina let’s you serve all of your models through the same Gateway while deploying them as individual microservices. You can also tie your models together in a pipeline if needed. Also some nice ML focussed features such as dynamic batching.

In this tutorial, I introduce Weaviate, an open-source vector database, with the thenlper/gte-base embedding model from Alibaba, through Hugging Face's transformers library.

This will be solved in Weaviate https://github.com/weaviate/weaviate/issues/2424

Link to GitHub -->

Hey @rvrs, I work on Weaviate and we are doing some improvements around increasing write throughput:

1. gRPC. Using gRPC to write vectors has had a really nice performance boost. It is released in Weaviate core but here is still some work on do on the clients. Feel free to get in contact if you would like to try it out.

2. Parameter tuning. lowering `efConstruction` can speed up imports.

3. We are also working on async indexing https://github.com/weaviate/weaviate/issues/3463 which will further speed things up.

In comparison with pgvector, Weaviate has more flexible query options such as hybrid search and quantization to save memory on larger datasets.