Redpanda Cloud - Annual Commits (BYOC & Dedicated/Serverless)

My main use case for Redpanda  is primarily for streaming, and I am currently focusing on building data lakehouses because I find them really interesting.

Redpanda  fits into my data lakehouse setup by normally fetching a source of data and mapping and transforming the data, so there are many ways to do that. I am exploring the possibilities of Redpanda, such as mapping the data with Redpanda Connect, or as an alternative, implementing my own solution. There are several ways to approach this. Additionally, I can sync the transformed data into any other destination, which really helps. Redpanda, through Redpanda Connect for instance, makes that really easy, and I am exploring those possibilities.

I have many areas to add about my use case or how I am experimenting with Redpanda. It is not about the streaming itself. It is about configurations, schemas, schema evolution, schema drift, how to map data in many ways, as well as configuration for governance, deployment, security, and control access. There are many areas that I would like to deep dive into and to control and to learn that I find really interesting in general with Redpanda. I think it is a really good software. As an alternative to Kafka, I think it is an amazing drop-in, and with one binary. That is a real advantage because other alternatives are really heavy. I see Redpanda as really light in that sense, so it is an amazing product.

The best features Redpanda offers start with its single binary, which helps a lot. Managing Redpanda through the command-line interface is a really big advantage. Having one binary, a UI, and a dashboard with the configuration helps a lot as well. The command-line interface and the UI are amazing, apart from the configuration regarding streaming, topics, and queues. That is for sure the strongest feature, but for me, it is not about the topics themselves. It is about other areas where I can control, view, and manage.

The command-line interface and the UI have made my work easier by allowing me to deal with topics or with configurations really easily, issuing commands. When I am dealing with CI/CD pipelines, I can issue the commands easily and configure anything. That is really helpful and is one use case, for instance.

Redpanda can be improved in several ways, and the more I experiment with the product, the more limitations I find. I understand that this is about business, and the product should grow, and they have to make money. That is certain. However, I would like to have more freedom in terms of having plugins to operate in other fields. For instance, if I am learning Apache Iceberg and I want to have a connector to map data to or to sync data to Apache Iceberg, that is a paid connector. That is a limitation. I could pay for a subscription, but I am under a testing phase to be sure that this is the product I want. There are many paid connectors and operators that it would be great to have as free alternatives. I can understand it is the business model.

I see positive impacts from Redpanda as it makes all the processes that streaming and mapping have easier. In general, I think it is really easy to install, to manage, and to deal with. It is a really great product.

I could not find a way to query the topics in Redpanda, something similar to what Apache Kafka  has with ksqlDB or something equivalent. I think Redpanda added that feature recently, but I am not sure if that is paid or free. I would like to test that as well, just to have topics with data and query for visibility and for other purposes. I would like to explore that, but I am not sure if that is a paid feature or a free one.

I have been working in my current field for more than 15 years.

Redpanda is stable in my experience.

Regarding Redpanda's scalability, I could not test that, so I do not have any opinion on that. I read that it is pretty stable. The performance is amazing. I read about the experiences of other companies using it, and their experiences are great and awesome. However, I could not test that on my own. I hope to do that soon, but so far I could not.

I think Redpanda has really amazing customer support based on my experience and from what I have read. I find the AI guide that Redpanda's website has really awesome. That is really helpful. By asking a question, I can solve many issues, doubts, or any comments that I might have. That is a pretty amazing solution.

I previously used Apache Kafka , as everyone is focused on it, and recently, all the changes that Apache Kafka had regarding Zookeeper and Kraft are amazing. It is always a good option to learn alternatives, to broaden my experience with other solutions, and to experiment with other solutions, just to confirm and state my feelings about the product and to discover new features. There is always an edge to using other products. My motivation was to check an alternative and to learn from this alternative because I had my vision and my experience with Apache Kafka.

I have seen a return on investment and personal gains since I started using Redpanda. For instance, for local projects and to experiment, I find the investment is really amazing because it is really quick to install and operate with. I can experiment in a minute. There are tons of examples.

Regarding my experience with pricing, setup cost, and licensing for Redpanda, I am exploring the product. If I am convinced about the product and the capabilities, and I am sure I will be because I find the product really amazing, for sure I will acquire a license to operate on other paid features if I like them. That is something that I strongly consider for the future, even for a personal project, not for a professional enterprise project. So far, I cannot state any opinion on pricing or setup cost.

I evaluated other options before choosing Redpanda, but mostly queues and not publish-subscriber options such as RabbitMQ or Azure  Queues, but not as publish-subscriber. For publish-subscriber, I only know Apache Kafka and Redpanda.

The first advice I would give to others looking into using Redpanda is that it is a binary, so it is just installing, and it is ready to use. That is amazing to start with. Redpanda's page contains amazing information. The AI question-answer solution is amazing as well. I can have a solution with one click to whatever concern I have. That is amazing as well. There is plenty of documentation with examples. I think it is really quick to operate on Redpanda in minutes.

I have additional thoughts about Redpanda. I want to say continue this work. Redpanda is amazing. I love it. Please continue with new features and improvements. I think Redpanda will dominate the market in the future, and it will be a really strong contender regarding streaming and AI. I hope so. You are really doing a great job. Continue with this, please. I would rate my overall experience with Redpanda as a nine out of ten.

I have been using Redpanda  at Model Cover for around three years, but I believe you should rely on better information. Redpanda  is not the best technology available on the market. Agent technology is currently the trend. Redpanda helps my organization solve problems related to big data pipelines and microservices mostly.

I feel Redpanda performs properly for big data pipelines and microservices. It can handle most of the requirements that are given, but it is still a little bit outdated. There are better open-source alternatives available.

I would like to add that Redpanda is mostly very good for streaming data. This is excellent for streaming data and it is faster than most alternatives, and without JVM, which is beneficial.

Redpanda has positively impacted my organization by enabling MVP fast to production. I can share that it has made things three weeks faster.

I have seen positive outcomes including improved efficiency, cost savings, and better performance metrics because it is open-source, fast, and good. There is also cost reduction.

I think that Redpanda's accuracy and reliability of output are good because it is Apache Kafka  compatible, making it very scalable.

I think Redpanda fits enough for what it is made for, so there is nothing to improve at the moment. I chose 8.5 to 9 because I think maybe building something from scratch in my case would make more sense because this is what we ended up doing. However, it takes considerable effort. It depends on the available resources. If you do not have many resources, you can go for it.

I have been using Redpanda for two years.

In my experience, Redpanda is stable.

Redpanda's scalability is proper. It is properly scalable and you can simply put it on a Kubernetes  Pod or Docker  Swarm and scale horizontally or vertically.

Customer support for Redpanda is open source. I did not have any interactions with their team, which may be an issue.

I did not use a different solution before Redpanda.

My experience with pricing, setup cost, and licensing for Redpanda is that it is straightforward with fast deployment.

I have seen a return on investment with Redpanda because we saved some resources.

My experience with pricing, setup cost, and licensing for Redpanda is that it is straightforward with fast deployment.

I did not evaluate other options before choosing Redpanda. Alternatives such as building from scratch or Kafka standalone were not considered.

Regarding Redpanda's AI capabilities, if your infrastructure is secure, you are fine and good to go. It is really good.

My advice for others looking into using Redpanda is to go for it.

I have additional thoughts about Redpanda: there is an over-focus on the topic, and that is the only feedback I have.

I have given this review a rating of 8.5 out of 10.

My main use case for Redpanda  is for event management in infrastructures that are not so robust or oversized that they would need a more voluminous Apache Kafka  environment, such as an on-demand retail event management system to register and receive sales lines in a retail flow.

I implemented this retail event management flow using Redpanda  to build the most minimalist infrastructure possible to avoid oversizing with Apache Kafka , removing unnecessary artifacts such as Zookeeper management and more complex management related to systems like brokers. Since it was only a simple management of sending and consuming events from consumers and event receivers, Redpanda provided a quick and scalable solution in a reasonable time.

The best features that Redpanda offers include the absence of Zookeeper and self-management of the infrastructure to avoid determining which is the parent node and all resizing in case of a failure, resulting in much more transparent fault tolerance to the user.

I have noticed this transparency in daily use by abstracting through Docker  containers or infrastructure such as Kubernetes , where management is very simple: I simply provision the infrastructure and register it, allowing quick scalability without the need for extensive technical knowledge of the infrastructure.

Redpanda has positively impacted my organization by being easy to implement quickly for use cases such as the implementation of MVPs and PoCs, making scalability, tolerance, and availability very interesting and facilitating the provisioning of infrastructure efficiently.

Redpanda needs more visibility and primarily greater access to documentation. Although the user-friendly documentation provided is fairly good, making it easier and better known is important, along with breaking the hegemony of Kafka.

I have been using Redpanda for a few months over the last few years.

I consider Redpanda to be a stable solution.

I would rate the scalability of Redpanda as good, but it is not as complex and customizable an infrastructure as Apache.

I previously used Apache Kafka before implementing Redpanda.

I decided to switch from Apache Kafka to Redpanda not as a complete replacement, as it still coexists in the organization, but it has been optimized in some use cases where Redpanda could be more interesting.

Before choosing Redpanda, I evaluated options such as RabbitMQ, Kafka itself, and some other alternatives that had been considered.

My advice to other professionals considering using Redpanda is to give it a chance, as it is an interesting solution that does not always require opting for more common solutions, being easy to use with a not overly complex onboarding process and a manageable learning curve. I am very happy to have used, tried, and experienced Redpanda. I would rate this review a seven out of ten.

My main use case for Redpanda  is streaming once data. I use Redpanda  for streaming data by supporting streaming to various data providers, putting it in Parquet format, structuring it, and sending it to the streaming infrastructure.

Redpanda helps us solve Iceberg and data storage with very low latency. The best features Redpanda offers are low latency, Iceberg, and a low infrastructure footprint.

Iceberg makes the biggest difference for my team, and it impacts our daily work by managing the Iceberg process. Regarding the features, it is very scalable and very easy to integrate into the ecosystem.

Redpanda has positively impacted my organization because the process is now easy and we have not used another streaming platform for comparison, but it has been better than Kafka. The process is easier now because the infrastructure footprint is less since it is written in C++, so it needs fewer resources.

Redpanda can be improved as the support they provide for BYOC could be better. They should support the REST catalog for Iceberg better since it is only partially supported in most cloud or hyperscalers.

I have been using Redpanda for a year.

I would rate Redpanda a nine out of ten. I chose nine out of ten because the support and the REST catalog not being there or not fully supported for Iceberg kept it from being a perfect score.

I have never used Redpanda's AI capabilities regarding its governance and security. I have never used Redpanda's AI capabilities to evaluate its accuracy and reliability of output either.

I do not have anything else I think Redpanda could improve or any other challenges I have faced with it. My advice to others looking into using Redpanda is to consider it. I recommend that you do your own analysis with other streaming providers to see if it meets your needs.

Redpanda is a good product that works well and I had no issues. My overall rating for this product is nine out of ten.

My main use case for Redpanda  is streaming to deduplicate my jobs.

To give you a specific example of how I use Redpanda  to deduplicate my jobs, we connect to vendors, grab files that are on their system, and pass it through Redpanda, which will deduplicate and indicate whether we have already seen this file. If we have, we do not start the job; otherwise, it will proceed to start the job to download those files.

The best features Redpanda offers include the ease of building inputs and outputs.

The ease of building inputs and outputs has made my work easier because I can quickly set up a new input or output without having to write extensive code; I can simply set up the configuration and it runs.

Redpanda has positively impacted my organization by allowing us to move from a batch approach to a more streaming approach for our jobs, which cuts down on our delivery time and allows us to better meet our SLAs for our clients.

One issue I had with Redpanda was debugging an issue where our API would stall whenever we output to our API, and I was not seeing anything in the logs explaining why it was taking a long time. It would be helpful to see trace logging in Redpanda waiting for the output response, which would help debug that issue.

I have been using Redpanda for about a year and a half.

Redpanda is stable.

I have not had any issues with Redpanda's scalability.

I was previously using Dolphin Scheduler, but I switched because I wanted streaming as opposed to batch or micro-batch.

I use Redpanda Connect, and I have not had any issues with the setup cost.

Before choosing Redpanda, I looked at Kafka as well, but I had experience with Redpanda, so I went with that.

My advice for others looking into using Redpanda is to rely heavily on the documentation, as it is very useful. I rate this product 7 out of 10.