VMware Tanzu Data Solutions Reviews

The use case involves the transferring of messages between services. It includes asynchronous messaging and I also need messages flowing to multiple microservices. In this case, it's basically a fan-out mechanism.

RabbitMQ is configurable and quite flexible.

The performance is fast and reliable.

It is easy to use. The addition of more queues and more services can be managed very easily.

There are some security concerns that have been raised with this product.

The configuration works with a config file, where all of the controls, including that of the administrator and user access, are stored there. The security isn't very stringent or very elaborate.

RabbitMQ is a stable solution.

This is a scalable product. There are six or seven services that are connected and using it.

I have not been involved with anything that necessitated contacting the support team.

Previously, we were using MSMQ, which is the Microsoft Message Queuing service. However, with the new version of .NET 4, support for MSMQ was no longer available. We could no longer get the libraries. As a result, we had to switch to a different queue mechanism. 

I have also used Azure Queue.

The initial deployment was quite easy. It took less than half an hour to get it up and running.

I deployed it myself.

The pricing for RabbitMQ is reasonable. It is worth the cost.

We researched ZeroMQ, RabbitMQ, and Kafka. We found that Kafka was a bit of an overkill because our requirements were quite simple. RabbitMQ was pretty easy to set up, which is why we chose it.

My advice for anybody who is implementing this product is to establish your users and exchanges properly.

In general, I'm quite comfortable with RabbitMQ. It satisfies my requirements and the main complaint I have is about the security.

I would rate this solution a seven out of ten.

• Transaction processing between microservices
• Message queue integration with Spring and RPC over Rabbit.

• Quick and simple to implement

• Easy to build proof-of-concept modules based on working examples from Pivotal.

• Out-of-the-box setup and configuration
• Great documentation and support from Pivotal
• Very useful management console

• Difficult to integrate with automated test and CICD 
• Moving beyond basic configurations can be challenging
• Not clear how to implement durable subscriber connections
• Not clear how a Rabbit service restart allows subscriber auto re-connect
• Service cluster failover depends on shared disk infrastructure.

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.

• The publisher and consumer ACK
• High availability
• Queue mirroring
• Exchanges and topics
• Supported programming languages with well-tested libraries

It provides us with a much better scale. We have never lost a single message with RabbitMQ.

The shared RabbitMQ Cluster has improved stability and maintainability of each application. We only have one message bus now.

I want it to reorder messages in a queue, if possible. If you could reorder messages in a queue directly, then you would not need a sequencer to reorder messages outside of RabbitMQ.

I have used this solution for seven years.

There were no stability issues.

There were no scalability issues.

We haven’t needed to use any support yet.

Initially, we were using the BizTalk and Redis solutions. The reason why we switched over was because we were looking for better support in Celery task management and other programming languages. We were looking for a much more stable and secure solution.

It is very simple to set up for basic usage. Clustering is a bit more complex, but it is also easy to do.

The RabbitMQ open source version works fine for almost all the use cases that I came across.

We looked at the Redis solution, but it was not a good fit for our needs.

Read the documentation and follow best practices. Make sure Erlang is up to date!

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.

Our primary use case is as a messaging broker between enterprise applications. It makes for reliable and secure communication.

The most valuable feature for me is that it is open source. The licensing costs are really low and they are transparent. You know how much you are going to pay if you want the commercial version. If you want the open-source version, you do not have to pay anything and that is just as reliable as the commercial one.

I would like to see the performance of the administration portal improved and additional messaging protocols.

I have been working with VMware RabbitMQ for the past eight years.

It is highly stable, reliable, and persistent.

VMware RabbitMQ is definitely scalable.

Technical support is excellent.

Positive

The initial setup was very easy and takes about five minutes to install.

If you want to pay for the licensing it costs eight hundred dollars per CPU core annually with the support.

I would give the following advice prepare a demo, with the vendor and check if it really applies to their needs. I would rate VMware RabbitMQ a nine out of ten.