What is our primary use case?
We use Chroma for RAG (Retrieval-augmented generation).
What is most valuable?
The solution's most valuable feature is its documentation, which allows new users to easily learn, deploy, and use it. Chroma has different similarity measurement algorithms that come in handy many times.
What needs improvement?
I think Chroma doesn't have a ready-made containerized image available. Maybe they do, but we have never used it that way.
For how long have I used the solution?
I have been using Chroma for ten months.
What do I think about the stability of the solution?
Chroma is a stable solution.
What do I think about the scalability of the solution?
Around 30 people from my team are using the solution in our organization.
Which solution did I use previously and why did I switch?
Compared to Milvus, Chroma is something easier to learn.
How was the initial setup?
The solution’s initial setup is very easy.
What was our ROI?
Without the solution, my developers would spend a lot of time struggling to understand the complexities of using certain systems. This can defocus them from implementing actual business requirements. Because of Chroma's simpler nature, I am able to deliver things faster, which leads to a better return on investment.
What other advice do I have?
If I have to deploy my application in a scalable environment with lots of data and users, I sometimes need to create multiple instances of my database or have a distributed database across different machines. Using Kubernetes, I can quickly increase the horizontal spread of Milvus because it is containerized and readily available. I don't have to do anything by myself.
New users can go to Chroma's 'Get Started' page and follow it like a tutorial. Then, they will be ready to use the solution. Chroma has helped us reduce the overall project post production time.
Overall, I rate the solution an eight out of ten.
Which deployment model are you using for this solution?
On-premises
