VMware Tanzu Data Solutions Reviews

With RabbitMQ, I appreciate that it's an open-source platform. 

RabbitMQ provides access to SDKs for development and the ability to raise and log tickets if we encounter issues. We can integrate RabbitMQ using various languages like Java or Python using the provided SDKs.

By comparison, Anypoint MQ it is a bit difficult. It's not open-source, so we have less flexibility. It's tightly coupled inside the Anypoint platform. This gives an advantage to clients already heavily dependent on the Anypoint platform, as they can easily adopt Anypoint MQ. 

Aside from that, Anypoint MQ is generally well-optimized inside Anypoint. Other aspects like reliability are standard across queueing systems. 

I haven't encountered any issues with the features I've used within the queueing functionality. Since queues provide message reliability, that's our primary concern.

RabbitMQ integrates easily. It's open-source and provides the required SDKs for development.

Overall, the aspects I've used – queues and monitoring – have been up to the mark.

Implementing a circuit breaker scenario using RabbitMQ is complicated. This complexity arises because manual intervention is required to manage worker details and handle operations based on worker IP addresses.

The use of public and private ports, specifically HTTP 8082 and HTTPS 8092, introduces complexity.

So, we had thought about moving away from RabbitMQ to Anypoint MQ because there is a complex scenario where we need to implement a circuit breaker. 

Using RabbitMQ is getting complicated, so we need to implement it manually. Anypoint MQ is well-optimized within the Anypoint platform itself. Anypoint MQ is a Mule-related broker, so it's very well optimized for the Anypoint platform itself. So, it will be easy if we are using Anypoint MQ; we can implement this circuit breaker scenario in a very easy way.

But because using RabbitMQ, it is a bit complex, because we need to get the details of the worker and we need to catch, we are stopping the worker based on how many workers we are having by getting their IP addresses, and this stuff is getting pretty much complicated. Then, all this stuff will work when you are on HTTP's public port 8082. But in general, we won't use public ports. HTTP 8082. We generally use 8092, which is a private port over HTTPS configuration. 

This will help us in several ways: the security purposes of the organization and everything else. So, that's why it's getting a bit complicated to implement this scenario while using RabbitMQ. So we got to move to Anypoint MQ.

We mainly create functions and scripts required for reporting.

The product is not complex; I do not have to create stored procedures, functions, or views. It's just simple to use.

We have two use cases for Tanzu; the first is for deep archiving where we're archiving a lot of data in petabytes and the second use case is for complex financial analytics for the regulators. We are customers of VMware Tanzu. 

Tanzu has cut our expenses because it doesn't use expensive hardware. We can store huge amounts of data in a single place and query that data quickly if regulators want to see older data. Carrying out large-scale analytics on a cheaper platform and getting it within 30 seconds is not easy. Tanzu helps us to achieve that. 

It is a stretched cache layer between two data centers. It allows active implementation. We put our application cache data, load it into memory, and make it accessible across multi-data centers.

The solution improved our site reliability.

I use the solution in my company for internal development. My company uses VMware RabbitMQ to develop an internal platform. In order to communicate with each other in our company, we use VMware RabbitMQ.

The most valuable features of the solution stem from the fact that it is flexible, resilient, and easy to improve and develop our company's projects.

I use the solution on cloud and bare metal servers for our company's cloud-native application development needs.

My company's IT personnel work with VMware products since we have its license.

Speaking about the features that have proven to be the most effective for managing database operations, I would say that RabbitMQ is used for the middleware layer, which will give good performance in terms of TPS and availability.

We use it to achieve what we call asynchronous processing. Asynchronous processing is where applications need to communicate with each other, but they don't need to rely on failures, maybe network failures, or dependencies between them. So how you do it: one application publishes a message to VMware RabbitMQ , and another application will consume that message from VMware RabbitMQ. And so do much, its processing. 

I'm in payments. Let me give you some background on Africa. In Africa, you normally use mobile services, often called Momo, to make payments. So basically, money sits in the customer's wallet, and you need to send them a PIN prompt for them to authorize the transaction.

Now you think about it. If you are on checkout, you need to click on a button to check out. Then, there's an intermediate API that will receive your request. Now, if that API had to call the service provider to issue the PIN prompt, then that takes about one minute. So what you are doing, you are creating a latency of one minute or sixty seconds between your checkout page and the provider.

So, how have we done it on our end? When checkout calls the API, the API publishes a message to RabbitMQ and sends a request back to checkout within 20 milliseconds. And tell the customer that, "We sent you a PIN prompt. Please approve." Now, the consumer who will pick that message up is the one to call the service provider.

Moreover, clustering is actually good because you don't need to have just a single instance of RabbitMQ, which then becomes a single point of failure. In our setup, we actually have two instances for our RabbitMQ cluster. What that means is if one instance is down, we have the other instance which is still processing.

We were using it as a high-volume text messaging solution. 

It's fully open source, has a high throughput, and the serviceability is good.