The main use case is a message stream. Just to process the data with window processing.
External reviews
External reviews are not included in the AWS star rating for the product.
Takes less resources compared to Kafka and it is based on C++ and is native to the operating system
What is our primary use case?
How has it helped my organization?
Operationally, it is good.
Two projects use artificial intelligence in combination with Redpanda right now.
What is most valuable?
The best thing is that it takes less resources compared to Kafka. We have a bad experience with Kafka; we need to restart the services because it's built on Java and requires a huge space on servers.
Redpanda is based on C++ and is native to the operating system. Basically, it is memory efficient. We like it.
It's easy to learn to use Redpanda for the first time because it supports the Kafka client as a developer. It supports native Kafka clients.
And from the operations perspective, it's a pretty standard installation. The online community support is also available.
What needs improvement?
The command-line tools need to be improved. To quickly check the status of the topics and all.
For example, if I wanted to check how many messages are in a topic, there is a command, but we need to use different tools to get that information. It's not really built into the native tool.
For how long have I used the solution?
I have been using it for three years. I use version 23.3.
What do I think about the stability of the solution?
I never experienced any bugs. So far, so good.
What do I think about the scalability of the solution?
I tested it with ten-plus nodes, and it's highly scalable.
We are about 55 people, 12 people actively use it, and we use it for six products.
How are customer service and support?
I never needed to contact the customer service and support because it's working as expected.
Which solution did I use previously and why did I switch?
We opted for Kafka for two reasons.
- One is we used to use Kafka, and we had to restart Kafka every quarter or so due to memory issues.
- Compared to Kafka, Redpanda is stable and resource consumption is also very effective. It takes less resources compared to other tools.
How was the initial setup?
It's very easy. The cluster setup is also very easy in Redpanda compared to others.
What's my experience with pricing, setup cost, and licensing?
It's free. Everybody can use it, only support is paid.
Which other solutions did I evaluate?
We evaluated three: Kafka, Redpanda, and ActiveMQ.
What other advice do I have?
I would recommend Redpanda to others because it's easy to set up, consumes less resources, and is stable compared to other tools.
Overall, I would rate it an eight out of ten because there is room for improvement. So far, it's nothing but a rewrite of Kafka. It needs improvement on some of the command-line tools. And the second thing is it doesn't have a management graphical user interface. That also needs improvement.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Affordable, easy to deploy, and it is easy to find things on the user interface
What is our primary use case?
We use the tool for a simple use case. We use it for data streaming and data normalization. We receive a lot of messages from many different systems. We normalize them and highlight errors. We get 5000 to 6000 messages per minute, so we dump them in the database to handle the load. We use the tool for microservices.
What is most valuable?
The UI is modern. It is simple. We find what we are looking for.
What needs improvement?
The version control mechanism must be improved. Converting messages takes time. There is a version mechanism in the tool. It follows the coding standard, but sometimes, it gets confusing because I have to remove the older version to ensure the new version works fine.
For how long have I used the solution?
I have been using the solution for more than a year. I am using the latest version of the tool.
What do I think about the stability of the solution?
The product is pretty stable.
What do I think about the scalability of the solution?
We have around 20 users.
Which solution did I use previously and why did I switch?
We used RabbitMQ before.
How was the initial setup?
The setup is straightforward. The vendor takes care of everything. We just paid for the tool and started using it.
What's my experience with pricing, setup cost, and licensing?
Redpanda is cheaper than its competitors. It is cheaper than Vanilla Kafka and Confluent.
What other advice do I have?
We use the libraries in the different programming languages. We use the message format in Avro, convert the data in the format, and pass it on. We have contacted the sales team about the solution. So far, the product fulfills our requirements. We get lots of data. The data flows through Kafka to Redpanda. Then it goes to a database.
If our infrastructure goes down for a week, we will not lose data. It is an advantage of Redpanda. I recommend the product to others. We might choose a different solution if we find something cheaper. We used Redpanda because we did not want to self-host our software. Redpanda is a piece of infrastructure. There is not much of a learning curve.
Overall, I rate the tool an eight out of ten.
Which deployment model are you using for this solution?
Solid product with great and efficient support
The support team is great and guides you through every step during the integration, and being able to deploy it in our cloud infrastructure /BYOC) was also a critical feature for us.
To sum it up: Great product, great support!
It hhelped us migrate our stack from a batch-oriented architecture to an event-oriented architecture.
Great low cost alternative for kafka compliant data streaming
The other real benefit comes from the pricing. Redpanda has allowed my small team the flexibility with learning as we build out our platform without worrying about going through our entire budget in a week or two, whereas some other data streaming platforms require an ironclad understanding of how much data you're putting into the system.