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.

The security is great. The interface is nothing special. The support hasn't been that great. You need to go online yourself, to the developer community for support. But apart from that, I think it's fairly secured, quite robust, and stable so far.

Their implementation is quite tricky. It's not that easy to implement RabbitMQ as a cluster. It would be great if they could improve that. 

I have been using RabbitMQ for three years. 

It's quite stable.

It is very scalable. I have a team of 10 developers who are using it and I have some of our clients using it in our Cloud cluster. We have about 10 banks running on the platform now.

I would rate their support as a five out of ten. It has room for major improvement. 

The initial setup is quite straightforward. It can be done within a few hours. 

I would recommend it, but I think there should be a proof of concept for the developer team to get their hands around it and have full control of it before they go into production.

I would rate RabbitMQ a seven out of ten. 

In the next release, I would like for them to improve the UI.

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.

I primarily use the solution for research purposes. I've utilized it for my academic studies for comparing HTTPS protocols. RabbitMQ supported the protocols I needed and I've read also that it's one of the most commonly used broker services.

The solution has really cool features to use. Its management console is excellent. You can utilize plugins to view the performance of the whole service on one network. It's wonderful. I really like it.

I was struggling with installing a few things. It would be good if was somewhat similar to RedHat. There should be more documentation regarding installation troubleshooting.

It's pretty straightforward, the setup, but it would be useful to know what to do if you do face certain challenges. Right now, without more in-depth documentation, it's unclear.

I've been using the solution for about one or two months. It's rather new to me.

The solution is very stable, from what I've witnessed so far. It's also a very fast system.

I haven't scaled the solution myself, so I can't speak from personal experience. I have heard that the solution is not so simple to scale because there is a core node beside the solution. There's some sort of smoothing methodology when it comes to the messaging, so I assume it's not so simple.

I've never contacted technical support for assistance.

The initial setup was simple. The first time I installed it, I installed it on Windows. For me, it took about one hour. If a user was facing a few problems, I'd say it could take up to two hours. Typically it's pretty quick to set up because the recommendations are pretty good.

I handled the initial setup myself.

I was considering using ActiveMQ on AWS, but after some research, I decided RabbitMO was a more complex solution and one that is more commonly used, so I chose RabbitMQ over it.

I'm only really using the solution for the purposes of research. I've just installed and am working on the latest version. My interest in the solution is purely academic, so I can't speak to how it would function within an organization.

I'd definitely recommend the solution, especially over HTTP in the Nico services platform. I've done my research and have discovered it's two times faster and more commonly used. It's also really easy to use on the Nico services platform because all of the components are in the cloud.

I'd rate the solution eight out of ten.

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.

It's a good core database. Scalability and performance are very good. I also like the fact the solution is open-source, so you can use it free of charge.

Some integration with other platforms like design tools, and ETL development tools, that will enable some advanced functionality (like fully down processing, etc.) would be helpful in future releases. Also, if the solution could offer automated creation of DDL statements from power designers, for example, it would be very useful. 

It's a software, and like any software, it has some bugs. However, you can add new features to improve it. Overall, our customers, who are big telcos, have been very satisfied with the platform and with its stability and performance

Scalability is simple because it's an MPP database. If you need more processing power or you need more storage, you just add a few more nodes in the cluster. It works on common commodity hardware. You can use any type of server. You don't need to have proprietary hardware. It's fairly flexible.

The solution requires a minimum amount of downtime when scaling. You can even add additional nodes without any downtime at all. I'm not 100% sure, but I think you can just reconfigure it and the background processes, and Greenplum will do the redistribution of the data.

Technical support is very good. The model they are using to fund the development of their open-source product is via revenue from support for enterprise customers, so they are very attentive when issues arise.

The solution is very straightforward to set up and is also easy to administer and develop using other open-source tools.

It's open-source, so it's free to use.

I'm a partner that works mainly with enterprises. Mostly the partners are big telcos and we deal with tens of terabytes of data.

MPP and columnar databases are the future of the analytical landscape. The era of appliances is over, so implementation of an MPP database on-premises or on the cloud is the way to go. Greenplum is definitely one of the leaders in this area.

I would rate the solution eight out of ten. If they improved the integration with other platforms in the landscape I would rate it higher. 

We install this solution for our clients. At the moment we are in the middle of an installation for a data warehouse that will be used by a telecommunications company that is based in Lesotho. We have not gone into production yet, but we have used it in a test environment and it works very well.

We are a technology company, so we handle software development, software implementation, data warehousing, and business intelligence.

We are using the on-premise deployment model. In Africa, there isn't much adoption of cloud services, so most of our clients are expecting on-premise implementation.

We chose Greenplum because of the architecture in terms of clustering databases and being able to have, or at least utilize the resources that are sitting on a database.

The installation is difficult and should be made easier. Maybe if the process was simpler it would have a quicker adoption by other developers. This could also be accomplished by providing training aids, such as videos to help with installation or using certain features. There are resources currently available on their website, but you have to search through a lot of documentation.

Our expectation is that the scalability will be good, as it is one of the main reasons that we have invested in this solution.

To this point, I have referenced the material on the website but have not really interacted with technical support.

The initial setup of this solution is not very simple. You need to properly follow the steps in terms of getting the whole architecture put together. We have a team of five people who are working on different aspects of the implementation.

Currently, we are focusing on the data layer. Next will be the ETL layer.

We are using our in-house team to implement this solution for our client.

We have used Oracle and Microsoft SQL, but we haven't had much success. We found that Oracle was not as scalable and we were having some performance bottlenecks. Also, from a licensing perspective, Greenplum was a better choice. For all of these reasons, we have chosen to invest heavily in Greenplum.

I would recommend this solution specifically for the scalability. This solution has a more futuristic technology, as opposed to the old school kind of data warehousing. If people are interested in getting something that is more future-proof, then I would recommend this solution.

So far, we're comfortable with what we've seen. What we have configured is addressing our needs at the moment.

I would rate this solution an eight 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.