Apache Kafka Previous Solutions

294bf53a 7050 4633 bd52 249f8c4d01d7 avatar
Michael Silvi
Senior Software Engineering Consultant at a tech services company with 51-200 employees
No, we did you use a previous messaging system. View full review »
B94acfff c187 47f3 a11a 2f35bba4f243 avatar
Sean Hickey
Solutions Architect at a consultancy with 1,001-5,000 employees
We used traditional message queues and file semaphores. There was a lot of overhead with asynchronous messages being put into an order and making sure nothing got dropped. It required a lot of code and maintenance. View full review »
868fac92 ebf8 4953 a45c b94dc0d0ab3f avatar
Kevin Quon
Technical Architect at a tech vendor with 51-200 employees
We did not have any other previous solutions. Our project was green field and a new type of project development. View full review »
Anonymous avatar x60
Founder, CEO at a tech vendor with 1-10 employees
We didn’t have a previous solution. We started with Kafka and then switched to Amazon Kinesis (PaaS for Kafka). I think Microsoft Azure also released a competing service. View full review »
Anonymous avatar x60
Head of Engineering
The previous solution was not really an equivalent one. I have been using several messaging systems, but Kafka fits us better for a more scalable system. View full review »
96d1f61b 88f4 4be7 bf9e e3ce6b7d6f17 avatar
Ivan Dyachkov
Team Lead at a financial services firm with 1,001-5,000 employees
We used RabbitMQ before. It does not scale well. View full review »
Anonymous avatar x60
Java Developer at a media company with 1,001-5,000 employees
I think performance-wise, the product is very good and fits in our use case. We used other distributed message queues, but all products have their own use case View full review »
Anonymous avatar x60
Lead Engineer at a retailer with 1,001-5,000 employees
We switched from a previous solution mainly to reduce costs and to have a more scalable solution. View full review »
98daa8e2 c94b 4886 a904 8eece49fd0de avatar
Technical Lead/Project Manager(Consulting Apple Inc) at a tech services company with 1,001-5,000 employees
We were using ActiveMQ, which is just a messaging system. We are changing because of Kafka’s added value of scalability, retention, and high payload support. View full review »
D8cacc50 c74a 4062 b407 94a51a8ca547 avatar
Chandra Keerthy
Principal Software Architect at a tech services company with 11-50 employees
Kafka rendered itself suitable for our product offering. It supports all the necessary requirements for a real-time pipeline. View full review »
D94612f3 2860 4f98 8b91 b334119e0435 avatar
Dori Waldman
Big Data Lead at a marketing services firm with 51-200 employees
I used RabbitMQ and ActiveMQ. Kafka is the standard, so there is no question what to use (unless you need better performance, like in ZeroMQ). View full review »
Anonymous avatar x60
Senior Java Consultant at a tech services company with 501-1,000 employees
We started to use Apache Kafka with our application from scratch. View full review »
Fbc6d212 93a9 4393 a7b1 de1e33e98003 avatar
Jyothish Kalavoor Parambil
Hadoop Technical Lead (Assistant Consultant) at a tech vendor with 10,001+ employees
For big data, we did not have a previous solution. I have used Microsoft MQ for building traditional systems. View full review »
50918253 dfac 4b79 a431 4fe711a85fff avatar
Mehul Jani
Deputy General Manager, DevOps Manager at a tech services company
We previously used rsync, which was not real-time. View full review »
Anonymous avatar x60
Enterprise Architect at a logistics company with 1,001-5,000 employees
Apache MQ is different. It is a message bus (log rotate) than can manage more than 10,000 events/sec. View full review »

Sign Up with Email