VMware Tanzu Data Solutions Reviews

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.

Asynchronous messaging; supporting data integrations between multiple applications on behalf of our many customers. RabbitMQ allows us to elegantly fan-out data to a variable number of subscribers, with almost zero effort.

We have been able to set up a messaging system that facilitates data integration between the software modules that we sell.

RabbitMQ allowed us to do this quickly so that we could focus on the business requirements, rather than divert our efforts to message broker implementations.

Once the architecture was proven, we were able to return to the RabbitMQ message layer in order to implement an HA cluster with a minimum of problems encountered.

Our business now has a fit-for-purpose information hub that we can apply across our systems. As the customer-base grows, we know that the hub can grow with it.

RabbitMQ is a solid, widely-used messaging system with a low cost-of-ownership. It is open, but with commercial support potentially available from Pivotal if required. (We have never needed it.) There is also a strong online user community.

One crucial feature was guaranteed messaging. We needed a solution that we could trust to not lose data.

Its built-in clustering capability allowed us to configure it as a highly available message broker, so that we can have confidence in the resilience of our architecture.

It can be scaled as well, although we have not tested this.

After almost two years' usage in our production environment, I am impressed by how stable the platform is - even when running on Windows Server 2012. Sure, we have had to tweak our set-up here and there as we have learned a few operational lessons along the way but overall it is very good.

RabbitMQ is clearly better supported on Linux than it is on Windows. There are idiosyncrasies in the Windows version that are not there on Linux.

The documentation for the Windows version is also less plentiful and less accurate.

The online community clearly provides better Linux support, but this naturally follows from the smaller Windows installed base.

There are also some potential concerns about how we maintain high-availability whilst also scaling out.

We have had no stability issues.

We have not used the scalability features yet.

We have not used technical support.

No previous solution was used.

The initial setup was straightforward. The online documentation was adequate and there is minimal initial configuration required to get up and running.

After that, it is simply a matter of experimentation with the various features and learning as you go.

This is an open source solution.

We looked at MSMQ, NServiceBus, Azure Service Bus, and Apache Kafka.

I would recommend that anyone who intends to deploy RabbitMQ on Windows should first consider whether a Linux implementation is a viable option for their situation.

We use it for data warehousing.

For complex queries, which would normally take a long time, and for reporting, it is very efficient. It doesn't take a long time for the execution of any report for the end-user.

• It's one of the fastest databases in the market.
• It's easy to use.
• From a maintenance perspective it's a good product.
• The segmentation, or architecture of the product is different than other databases such as Oracle. So even in 10 years, the data distribution for such segments will not affect other segments.
• The query performance of the product, for complex queries, is very good.
• It has good integration with Hadoop and Big Data.

The implementation of an upgrade takes a long time. But maybe it's different from one instance to another, I'm not sure.

Also, one of the disadvantages, not a disadvantage with the product itself, but overall, is the expertise in the marketplace. It's not easy to find a Greenplum administrator in the market, compared to other products such as Oracle. We used to work with such products, but for Greenplum, it's not easy to find resources with the knowledge of administration of the database.

If we face any issues they're normal and we open tickets.

It's scalable. I would rate scalability seven out of 10.

We hired one DB admin for Greenplum. If he faces any issues he opens tickets with the vendor, but most of the issues, 90% of them, he is able to solve without support.

We used to other products before, but when we worked with Greenplum, as compared to other products on the market, we found it's a good product.

Before Greenplum, we used Oracle but it was mostly obsolete. So we had to upgrade our tools. We needed to have a database with an API tool.

I'm not a professional in the setup but setup of the environment itself was managed by us. We managed between development, testing, and production servers. We are able to maintain it. I don't think it is complicated.

Most of the issues can be solved without referring back to support. A very small minority of issues required support from the vendor.

Pricing is good compared to other products. It's fine.

We did a comparison among some databases, one of them Greenplum. We assessed features, did a comparison in terms of the price, then we chose Greenplum. And we've retained it. We've found it's a good product, to date.

Oracle Exadata was part of the comparison, as was IBM Netazza. In terms of quality and the price, compared to the other products, we chose Greenplum. Also, to be honest, at that time we got a good offer: Use it for the first year with a minimal price. Then they opened a support contract with us, later. That was one of the advantages.

I give it an eight out of 10. To bring it up to a 10, they need to interact more with customers. They need to explain the features, especially when there are new releases of Greenplum. I know just from information I've found that it has other features, it can be used to for analytics, for integration with Big Data, Hadoop. They need to focus on this part with the customer. 

Also they need to enhance integration with other Big Data products. They need to adapt more, give more features, because customers are looking for these things in the market now. They have the product itself already, but they need to integrate with Big Data platforms and to open a bi-directional connection between Greenplum and Big Data. They need to focus on these features more.

But, from my perspective, for what I'm looking for, I can say it's a good product. Most of the features I'm looking for are available.

I am still comparing RabbitMQ and Kafka, but based upon the information I have gathered RabbitMQ is an awesome tool.

RabbitMQ will help to remove a lot of the complexities and create a loosely coupled codebase.

I like the high throughput of 20K messages/sec, and that it supports multiple protocols. The flexible routing is great as well.

The next release should include some of the flexibility and features that Kafka offers.

I have used IBM MQ software, but it was not applicable to this application.

I have evaluated and researched Axon, RabbitMQ, Kafka, and IBM MQ.

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.

• High performance
• Integration with Spring Framework
• Easy installation and configuration

We have been using GemFire for a Telco project, which we need process network data in real time and meanwhile access some reference data. GemFire has done a great job, as we have managed to process over 200,000 messages per second.

In build monitoring, the interface could be improved.

18 months.

With version 8.1, we had some issues while we were querying data from memory, but it has been fixed in version 8.2, and after that we have never had problems.

No, even when we had serious network problems, GemFire managed to recover.

A nine out of 10.

No, GemFire was always good enough for us.

Initial setup was easy. In older versions, the user interface was not helpful, but it's improved lately.

As a developer, I was never a part of this pricing decision. That's why I have no advice.

No, because we've started to use GemFire as part of a real-time intelligence platform.

Trust GemFire and use the benefits of their strong documentation.