VMware Tanzu Data Solutions Reviews

Our primary use case is for telecom customers.

In terms of most valuable features, I'd say Pivotal Greenplum's shared-nothing architecture.

I'd like to see a bridge between Greenplum and Hadoop.

We didn't have any issues yet with stability.

In terms of scalability, I just have one master and two segment hosts.

Initial setup is a little complex. It took around two weeks to deploy.

I prefer an open-source solution but Pivotal Greenplum is cheap and has many functionalities.

On a scale of 1 -10 I'd rate it a 6.

It is a very good appliance for data warehouse (DWH) usage.

• Very fast for query processing
• Parallel load
• Polymorphic storage

Before we had Oracle Exadata, some queries would take more than 20 hours of execution. With Greenplum, it take a few minutes.

It will be very useful if we could communicate with other database types from Greenplum (using a database link).

Four years.

No issues.

No issues.

Good. I would give their technical support a seven out of 10.

Yes, Oracle Exadata. Performance was the main criteria for switching to Greenplum.

It was a simple setup.

It is the best product with best fit for price/performance customer objectives.

We evaluated Oracle technology that we used before.

I encourage other customer to try Greenplum, specifically for DWH use. It is a very useful product.

There are many valuable features, such as parallel loading and the solution's scalability.

It's allowed us to do a lot of data analytics with it that we weren't able to do before.

The performance needs to be improved.

As a whole, two years on multiple versions.

We've had no issues with deployment.

It's stable, but slowness is an issue.

It's scaled find for us.

Customer service is OK.

Technical support is OK.

No solution was used previously.

Implementation was done by a vendor team.

Pricing is pretty much OK compared to others.

External tables to load the data from flat files.

It helped us in loading millions of data in quick time & improved query response.

More stability in terms of query result.

Five years - DCA V2.0 EMC & Greenplum Database

No.

Not usually, but sometimes we do.

No issues encountered.

Excellent.

Excellent.

We applied MPP Appliance for the first time earlier we were running on SMP’s.

It was straightforward.

Vendor- they had good expertise.

Good.

We also looked at Teradata.

Very good and cost effective with very good customer support.

With VMware Tanzu Greenplum, one can make a huge database table and analyze the queries by adding in the SQL command. Some hint or command for the query goes over the multi-parallel execution. Also, queries can be sent quickly to other database systems.

VMware Tanzu Greenplum needs improvement in the memory area and improved methods for quick access to the disc. So, one of the quick goals of Greenplum must work on enhancing access to the disc by adding hints in the database.

I have been using VMware Tanzu Greenplum since 2017. I have installed the ring through the Dell Dell Platform, the EMC platform, and the DX100.

We use the VMware Tanzu Greenplum support directly, the community for open source Greenplum database. I rate it a seven out of ten.

Neutral

The initial setup was complex because of the architecture we used. Ten people are needed to maintain the product, of which eight are DBAs, and two support the operating system as the administrator.

For the support network of the product, overall installation, use of the database, and improved database and support, I rate the solution an eight out of ten.

Some valuable features of this product are:

• Message queuing
• Good support
• Provided scalability and a distributed environment
• Easy usability with NodeJS
• Could easily withstand and pass stress/load testing with more than 10K API calls
• Helped achieve a distributed environment and implement a 3-tier structure
• Helped to develop a highly scalable system by decoupling front end and back end

We had a project where we had huge responses to APIs from the front-end and had to handle such large responses/requests without losing any of them. RabbitMQ efficiently handled this problem by providing message queuing and decoupling our front end and back end.

I would love to see better documentation/demo for few technologies. There is need for better stability in the Windows environment.

I have used this product for around six months.

We encountered a few problems with Windows while clustering and hence we used Linux.

We did not encounter any scalability issues.

I would give the technical support a 7/10 rating.

It involved more of research as how to use RabbitMQ. For clustering, it was little bit complex but I was able to follow the documentation provided.

We did not evaluate any other solution prior to this one.

It gives product support with your technology.

We find authentication, performance, and durable messaging the most valuable features. Due to the nature of my use case, performance and security were of the highest priority and were the main reason I chose RabbitMQ messaging frameworks.

Over time, the most useful feature became the ability to create durable queues, which increased reliability and also boosted performance.

I would like to see improvements in fluent configuration. I'd also like to see more support for code-first environment configuration. We do a lot of this stuff as part of our deployment process via command line scripts, but I'd rather have a specific API to target rabbitmq.config and rabbitmq-env.config so that configuration could scale with my environments more easily. If more of that was baked into the RabbitMQ management HTTP API, it would help.

We have been using RabbitMQ for about 2 years.

We did not have any issues with stability.

We had no issues with stability. Exactly the opposite! It actually blew me away how flexible a framework it is. It’s a very elegant solution.

I never used technical support.

I've had the most success using NServiceBus over MassTransit. Look there for .NET Devs.

The primary use of this solution is for horizontal scalability.

We have an on-premises deployment.

The most valuable feature for us is horizontal scaling.

The deployment process for this solution could be made easier.

I saw some limitation with respect to the column store, and removing this would be an improvement.

This solution is stable enough. 

We are not yet sure about scalability, but we will see in the future.

We have not been in touch with technical support for this solution.

We were using MySQL prior to this solution.

The initial setup of this solution was not simple, but it was not too complex, either. I would say that it was of medium complexity.

Our deployment took approximately two days, although this was only a partial deployment. We have yet to add another node.

We performed the deployment in-house.

We are using the open-source version of this solution.

Prior to choosing this solution, we evaluated MySQL and PostgreSQL.

I would rate this solution a seven out of ten.