Share your experience using Red Hat Data Grid

We are in retail and marketing, and Microsoft Azure Cosmos DB gives us the opportunity as a retail industry to store catalog data. This is essentially used for event sourcing. In my department, it is particularly useful for our catalog data storage and marketing operations.

Microsoft Azure Cosmos DB has improved our overall search result quality. It is very easy to use Microsoft Azure Cosmos DB to search through large amounts of data. This is one of the advantages that I can mention with Microsoft Azure Cosmos DB, which is not available or accessible with other solutions. Searching and working with large amounts of data while using Microsoft Azure Cosmos DB is one of the biggest advantages it provides for enhanced business operations.

The aspect I appreciate most about Microsoft Azure Cosmos DB is the scalability. Horizontally, we can add as many servers as possible, which is very key for us as a company. Another important feature is that it is a globally distributed product that comes with numerous benefits. The real-time analytic features it offers, as opposed to structured query language features, provide real-time analysis for our retail and marketing operations. The integrated features, such as Azure Snipes link, enable easier running analytics for our operations. Additionally, we have noticed that it positively impacts our transactional performances as a company.

In terms of improvement for Microsoft Azure Cosmos DB, while it eliminates the burden of managing database infrastructure, we realized it might not be possible to use various models simultaneously as it only accepts a single model at any given point in time. This is an area that could be improved upon.

The operational complexity of Microsoft Azure Cosmos DB can be challenging for individuals who are not tech-savvy. Making it simpler for companies to navigate through various features would be beneficial for future development in terms of reducing its complexity. However, it remains a good product that eliminates many bottlenecks we experienced before in terms of database management, storage, transmission, and retrieval for our business.

While there is complexity in Microsoft Azure Cosmos DB, we have found that software experts and IT professionals who are passionate about the product can overcome these challenges. We have not yet achieved fifty percent in terms of training our staff due to its complexity. However, the benefits significantly outweigh the complexity, particularly in terms of database storage, management, retrieval, and transmission in milliseconds. The global access, real-time capabilities, and low latency in terms of turnaround time make it an excellent solution once fully embraced and deployed.

We have been using Microsoft Azure Cosmos DB for one year.

The initial deployment of Microsoft Azure Cosmos DB was challenging at the beginning, but we overcame these challenges and ultimately achieved positive results.

The performance and stability of Microsoft Azure Cosmos DB maintains low response times in milliseconds. It is fast, effective, and reliable.

In terms of scalability for Microsoft Azure Cosmos DB, the servers can be horizontally scaled, and we can add as many servers as needed. This capability is possible with Microsoft Azure Cosmos DB, which is not common in other solutions. This is a significant advantage of Microsoft Azure Cosmos DB.

It took us approximately three to four weeks to fully set up Microsoft Azure Cosmos DB and get it operational. Our company utilizes multiple software solutions, so integration was a key consideration. With a team of six to seven software developers, along with additional IT experts, we completed the setup within this timeframe, which we considered reasonable for this type of product.

Our company has multiple software solutions, and integration is a crucial aspect. We have a team of six to seven software developers, along with additional IT experts, who assist in working with these software solutions.

I have used SQL as an alternative to compare with Microsoft Azure Cosmos DB. Having Microsoft Azure Cosmos DB come with additional features beyond SQL capabilities was advantageous for our company's deployment.

I rate Microsoft Azure Cosmos DB a 9 out of 10 because there is always room for improvement in any software.

The benefits of Microsoft Azure Cosmos DB were immediate for us. It was within our budget, and we cannot say it constrained our finances because it was approved. The cost-benefit analysis shows that the benefits outweigh the costs. The maintenance costs are also within our estimated budgeted projections as a company.

I am willing to provide references for Microsoft Azure Cosmos DB and can be a reference for anyone interested in purchasing the same product. I am available to be contacted by Microsoft regarding this review should they have any questions.

We have many use cases. We are using Microsoft Azure Cosmos DB for our event streaming framework. We are using Microsoft Azure Cosmos DB to store all the event data for AI activities.

We are also using it for a RAG-based solution, though it is not entirely RAG-based. We are using Microsoft Azure Cosmos DB as a staging solution, and then we are using the AI search to index it and continue to the RAG for the LLM.

We are just using it as a staging solution. We have use cases for extracting huge documents, which can be more than 500 pages or even 10,000 pages. We cannot directly use the LLM, so we have to use a RAG-based approach. For that, we have chosen Microsoft Azure Cosmos DB and we are using the vectors there. However, instead of directly querying the vectors in Microsoft Azure Cosmos DB, we are indexing that in AI search.

The searching capability is exceptional. It is very simple and incomparable to competitors. With SQL, we have to install everything, but this is pretty quick. We have a Bicep template. Using the Bicep template to create Microsoft Azure Cosmos DB containers and partition keys makes everything convenient. Scaling is also convenient.

The RUs still appear to be a black box for everyone. Even though they explain read and write RUs, it remains unclear for many users. With Microsoft Azure Cosmos DB, we are using event streaming in the entire organization. We are using a framework for event streaming, and we suddenly reached a huge amount - the capacity of 20 GB partition key. When it reaches 100% of RUs, we face issues. We have to work on rebuilding the partition key. 

Regarding billing, we need better control. Sometimes it exceeds the forecasted budget. More clarity on RUs would be beneficial, even though documentation exists.

There is a 2 MB limitation for a document, which is a hard limit. Additionally, modeling in Microsoft Azure Cosmos DB is more challenging compared to RDBMS and other NoSQL solutions because we cannot store everything in one place. Since it's NoSQL, we sometimes need to split one document into multiple containers due to the 2 MB limitation.

I have been using it for more than two years.

Its stability is good. I would rate it an eight out of ten for stability.

Scalability is pretty good. I would rate it an eight out of ten for scalability.

I would give a low rating to Microsoft support, as whenever I talked to them, I never got a solution. I had to guide them.

If the support ticket lands in certain regions such as Sweden, they have more knowledge and the ticket gets resolved easily. At times, it moves between departments, requiring escalation to get the correct person involved.

The support team needs improvement in understanding who they are talking to. They should not ask basic questions when speaking with experienced users. I am deeply knowledgeable about Microsoft Azure Cosmos DB, which I have had to explain to the support team.

Neutral

It is very simple. We can't compare it with any competitor. We just use the Bicep template.

Its implementation takes a maximum of one hour.

Because of the lack of understanding about RUs, the costs become unpredictable. It sometimes goes over the budget.

Currently, they are implementing Fabric and OneLake solutions. Fabric appears faster. According to Microsoft representatives, querying in Fabric instead of Microsoft Azure Cosmos DB will be quicker. However, I remain confident in the querying capability of Microsoft Azure Cosmos DB.

It is pretty good, and currently, everyone wants to move from Microsoft Azure Cosmos DB to Databricks, but when I query data in Databricks, it takes considerable time with huge amounts of data. It stores in the BLOB in the backend, but when we use Microsoft Azure Cosmos DB, it retrieves the data much faster. The main consideration is being careful with fixing the partition key.

I would strongly recommend it for new projects. When you create a project from scratch, it is easy to implement Microsoft Azure Cosmos DB because the library is very pretty good. You can just use the library and create a container. I do not see any complexity at all in using Microsoft Azure Cosmos DB. 

I would rate Microsoft Azure Cosmos DB a nine out of ten.