MongoDB vs. Pinecone

If asked by a colleague I would highly recommend MongoDB. MongoDB provides incredible flexibility and is quick and easy to set up. It also provides extensive documentation which is very useful for someone new to the tool. Though I've used it for years and still referenced the docs often. From my experience and the use cases I've worked on, I'd suggest using it anywhere that needs a fast, efficient storage space for non-relational data. If a relational database is needed then another tool would be more apt.

Incentivized

Similarity search and ranking are fundamental capabilities, and Pinecone just has this nailed. Almost every application, especially those that talk to LLMs, can use this feature, and there is no reason to reinvent it or use anything more complicated or "full stack" than Pinecone. Pinecone is a powerful tool in this space.

Incentivized

• Being a JSON language optimizes the response time of a query, you can directly build a query logic from the same service
• You can install a local, database-based environment rather than the non-relational real-time bases such a firebase does not allow, the local environment is paramount since you can work without relying on the internet.
• Forming collections in Mango is relatively simple, you do not need to know of query to work with it, since it has a simple graphic environment that allows you to manage databases for those who are not experts in console management.

Incentivized

• Adding a vector (of course) and we are able to add arbitrary metadata with it.
• Similarity search, ranking and metadata retrieval.
• The webui/console tools are nice when debugging/confirming something. Above-average tooling in this regard.

Incentivized

• An aggregate pipeline can be a bit overwhelming as a newcomer.
• There's still no real concept of joins with references/foreign keys, although the aggregate framework has a feature that is close.
• Database management/dev ops can still be time-consuming if rolling your own deployments. (Thankfully there are plenty of providers like Compose or even MongoDB's own Atlas that helps take care of the nitty-gritty.

Incentivized

• Pinecone has come a long way (we have been using it for years). While the tooling used to have some rough edges, I can't really complain these days.
• Migrating an entire database from one AWS zone to another basically required a full data dump and reload. That could be improved. I have not tried AWS=>GCP=>Azure replications/migrations, but suspect they are not yet well supported, and that would be helpful.

Incentivized

I am looking forward to increasing our SaaS subscriptions such that I get to experience global replica sets, working in reads from secondaries, and what not. Can't wait to be able to exploit some of the power that the "Big Boys" use MongoDB for.

Incentivized

NoSQL database systems such as MongoDB lack graphical interfaces by default and therefore to improve usability it is necessary to install third-party applications to see more visually the schemas and stored documents. In addition, these tools also allow us to visualize the commands to be executed for each operation.

Incentivized

It is lean and covers all the bases. I am sure there are one or two things that could be better, so 9 instead of 10.

Incentivized

Finding support from local companies can be difficult. There were times when the local company could not find a solution and we reached a solution by getting support globally. If a good local company is found, it will overcome all your problems with its global support.

Incentivized

While the setup and configuration of MongoDB is pretty straight forward, having a vendor that performs automatic backups and scales the cluster automatically is very convenient. If you do not have a system administrator or DBA familiar with MongoDB on hand, it's a very good idea to use a 3rd party vendor that specializes in MongoDB hosting. The value is very well worth it over hosting it yourself since the cost is often reasonable among providers.

Incentivized

We have [measured] the speed in reading/write operations in high load and finally select the winner = MongoDBWe have [not] too much data but in case there will be 10 [times] more we need Cassandra. Cassandra's storage engine provides constant-time writes no matter how big your data set grows. For analytics, MongoDB provides a custom map/reduce implementation; Cassandra provides native Hadoop support.

We selected Pinecone because they had much more startup-friendly pricing.

Incentivized

• Open Source w/ reasonable support costs have a direct, positive impact on the ROI (we moved away from large, monolithic, locked in licensing models)
• You do have to balance the necessary level of HA & DR with the number of servers required to scale up and scale out. Servers cost money - so DR & HR doesn't come for free (even though it's built into the architecture of MongoDB

• When our product had a primitive search, we were lambasted by users, and we embraced Pinecone to fill an urgent need for something better. Over the years, it has become a wired-in foundation for more than a few product features.
• The money we didn't spend creating and maintaining something "like" Pinecone has been one of our best investments.

Incentivized