Apache Kafka is an open-source stream processing platform developed by the Apache Software Foundation written in Scala and Java. The Kafka event streaming platform is used by thousands of companies for high-performance data pipelines, streaming analytics, data integration, and mission-critical applications.
N/A
IBM MQ
Score 8.8 out of 10
N/A
IBM MQ (formerly WebSphere MQ and MQSeries) is messaging middleware.
N/A
Workday HCM
Score 7.8 out of 10
N/A
Workday Human Capital Management is a cloud-native system offering a globally
consistent user experience. Workday HCM is part of an intelligent, unified system with other
Workday products.
N/A
Pricing
Apache Kafka
IBM MQ
Workday Human Capital Management
Editions & Modules
No answers on this topic
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Apache Kafka
IBM MQ
Workday HCM
Free Trial
No
Yes
No
Free/Freemium Version
No
Yes
No
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
—
—
More Pricing Information
Community Pulse
Apache Kafka
IBM MQ
Workday Human Capital Management
Considered Multiple Products
Apache Kafka
Verified User
Analyst
Chose Apache Kafka
Confluent Cloud is still based on Apache Kafka but it has a subscription fee so, from a long term perspective, it is wiser to deploy your own Kafka instance that spans public and private cloud. Amazon Kinesis, Google Cloud Pub/Sub do not do well for a very number of messages …
Kafka is faster and more scalable, also "free" as opensource (albeit we deploy using a commercial distribution). Infrastructure tends to be cheaper. On the other hand, projects must adapt to Kafka APIs that sometimes change and BAU increases until a major 1.x version comes out …
Apache Kafka may be a better option in comparison with IBM MQ its real-time data streaming and large data payload service. It depends upon the specific requirement and meets those needs. MuleSoft any point platform is very easy to connect to various other types of platforms in …
I've also used Apache Kafka and RabbitMQ. Compared to these, IBM MQ offers superior reliability and transactional integrity, making it a better choice for complex, mission-critical enterprise environments where message delivery and security are paramount. We chose IBM MQ for …
Kafka is renowned for its impressive throughput, fault tolerance, and real-time data streaming capabilities. Nonetheless, IBM MQ remains the preferred choice due to its unwavering commitment to guaranteed delivery and exceptional reliability. Fault-Tolerant Architectures of IBM …
We found IBM MQ very easy to get started and quick to learn by the new users with a short learning curve and seamlessly integrates with IBM products, and quick to perform self-service analytics and make informed business decisions. IBM MQ is also very straightforward in …
IBM MQ is very stable and a proven product compared to other Messaging platforms available. Performance was better than WSO2 product and also the RabbitMQ. Though Kafka and IBM MQ is not directly comparable, Kafka is more suited for event based systems and also where there is …
Apache Kafka is well-suited for most data-streaming use cases. Amazon Kinesis and Azure EventHubs, unless you have a specific use case where using those cloud PaAS for your data lakes, once set up well, Apache Kafka will take care of everything else in the background. Azure EventHubs, is good for cross-cloud use cases, and Amazon Kinesis - I have no real-world experience. But I believe it is the same.
In the context of Internet of Things (IoT) applications, IBM MQ plays a pivotal role in managing the substantial data streams emanating from interconnected devices. Its primary function is to guarantee the dependable transmission and processing of data, catering to a diverse range of IoT use cases, including but not limited to smart city initiatives, healthcare monitoring systems, and industrial automation solutions. In the telecommunications sector, IBM MQ is employed for message routing, call detail record (CDR) processing, and network management to ensure real-time data exchange and fault tolerance. When managing the supply chain and logistics, IBM MQ is used to ensure timely and accurate communication between different entities, including suppliers, warehouses, and transportation providers. IBM MQ can be cost-prohibitive for smaller organizations due to licensing and maintenance costs. In such cases, open-source or lightweight messaging solutions may be more appropriate. For scenarios requiring extremely low-latency, real-time data exchange, and high throughput, other messaging technologies, like Apache Kafka, may be more suitable due to their specialized design for such use cases.
I would say it's well suited in every environment because I think it does so much. It's like the holy grail of HRIS systems is what I like to call it because thinking about all parts of the employee lifecycle, it lives here in Workday Human Capital Management. So I love the fact that you can do the people data analytics, you can store employee records, the talent acquisition pieces there. I'm thinking I can't think of anything negative right now except for the fact that I can't drill down into the data for the people analytics side. Other than that, I think it's literally, yeah, the holy grail of HRIS systems, I love it and I would highly recommend it.
Really easy to configure. I've used other message brokers such as RabbitMQ and compared to them, Kafka's configurations are very easy to understand and tweak.
Very scalable: easily configured to run on multiple nodes allowing for ease of parallelism (assuming your queues/topics don't have to be consumed in the exact same order the messages were delivered)
Not exactly a feature, but I trust Kafka will be around for at least another decade because active development has continued to be strong and there's a lot of financial backing from Confluent and LinkedIn, and probably many other companies who are using it (which, anecdotally, is many).
The documentation is very clear,It is understandable and the support helps to configure it in the best way.
Server guidelines make it possible to get the most out of work management. It's broad, we can work with different operating systems, I really recommend using linux.
It is highly compatible with systems, brockers, applications, and data accumulation programs, it is possible to configure everything so that after the installation of programs, they can communicate with each other and then throw data to an external program that accumulates it and represents in clear details of steps to follow and make business decisions.
Groups employees in management hierarchies and creates Org Charts that are easy to navigate and allow for visualizing management chains regardless of employee locations
Intuitive and easy to use. The Workday search functionality works very much like Google; one can search for anything that they have access to in the database and drill down into the various details. All information is connected through hyperlinks and users can easily keep digging into the details for as far as their security access would take them.
Tasks such as to do, review or approve items are sent to the user's Workday Inbox, very much resembling email. Notifications about outstanding "to do" items are also sent to each the user's work email address on a daily basis.
Sometimes it becomes difficult to monitor our Kafka deployments. We've been able to overcome it largely using AWS MSK, a managed service for Apache Kafka, but a separate monitoring dashboard would have been great.
Simplify the process for local deployment of Kafka and provide a user interface to get visibility into the different topics and the messages being processed.
Learning curve around creation of broker and topics could be simplified
There is limitation on number of svrconn connections you can have to MQ on the mainframe which has been an major issue for us. This has been an issue for us for over 4 years and still no fix although I am aware IBM have been working on a solution over the last year.
When upgrading to MQ V9.3 on our MQ appliances there is no fall-back option. This was the same for MQ V9.2 upgrade from MQ V9.0. For production upgrades this I believe is not acceptable.
AMS is not supplied as part of the standard mainframe MQ licence. You need an extra licence. IBM tell customers how important security and protecting data is yet they still want to charge for this software. The cost of MQ on the mainframe is not cheap so I would expect AMS to be part of the base product.
It is work to make one system the source of truth for our data, but now that it is done, there is less work involved in staying on this path. This means for us that maintaining and/or implementing new modules like performance, finance, talent, etc. is simple. It's a no-brainer
Apache Kafka is highly recommended to develop loosely coupled, real-time processing applications. Also, Apache Kafka provides property based configuration. Producer, Consumer and broker contain their own separate property file
I give it a nine because it has significantly improved my team's data reliability and operational efficiency. Its great security features give us peace of mind, knowing our sensitive data is well protected. While the setup might initially be complex, I believe the long-term benefits far outweigh this hurdle.
Workday's on a great path in terms of user experience. Their goals is to deliver a use experience that doesn't require training or instruction, like Amazon on the consumer side for example. That's hard to do when you're talking about complex business processes and important and sensitive employee information, but they're doing it well
The messages are delivered instantly with this software and it integrates with our technology stack, in terms of availability we only had one failure when we were doing some testing and integration with third parties, the features of this software make it always available and its deployment is easy for the company, it does not generate expenses due to failures
In 2014, Workday has changed the update process. There will be two updates a year; the updates will be delivered to customers typically in a 24 hour window during these two weekends a year. They also keep the Community up-to-date about any planned outages, etc. There is weekly scheduled downtime on Friday night.
From my perspective, the system runs like a well oiled machine and I have not had any issues with customers complaining about speed. If a report is taking long to run, the report can run in the background and you can go about your business. For larger enterprises, there is additional space and machines to process the application in what Workday refers to it as Extended Configuration Tenant
Support for Apache Kafka (if willing to pay) is available from Confluent that includes the same time that created Kafka at Linkedin so they know this software in and out. Moreover, Apache Kafka is well known and best practices documents and deployment scenarios are easily available for download. For example, from eBay, Linkedin, Uber, and NYTimes.
There are very specific things that must be elevated to more specialized areas of support, but the common support is very agile when receiving questions or when we leave concerns in real time. I recommend the support of the program in this regard.
Workday is still learning about the needs of higher education. I have seen rapid improvement in support and knowledge over the last year so am confident this will continue to improve. Overall however, I have found the Support Team to be extremely responsive and Workday offers the advantage of having support across several timezones so that we never wait more than a few hours for a response.
Some training is offered online. Cost is per-person. This also gets quite expensive. Training doesn’t follow a logical path A to B. Starts in middle. When you try to do it afterwards at your desk, difficult. • Training scenarios are not very real
I have done for report writing and mass imports (EIBs). They give materials and you run through examples, i.e. you don’t just watch them do tasks, so that is helpful. Training is expensive – a single reporting writing class is $600 per person for virtual training
It was implemented before my joining the company. At my last company, we used Workday professional services.
Based upon my experience at my last company, I would rate the implementation experience an 8/10. There are different ways to set things up and we had different people telling us different things. It set us back a couple of times.
Regarding configuration advice, we could set things up where every manager has supervisory organizations, or have it financially based i.e. aligned to cost center/department. We chose the individual manager path and I think we should have chosen a department route. Going down the individual manager path, to maintain the information, we have to inactivate a supervisory org whenever a manager changes/leaves.
I used other messaging/queue solutions that are a lot more basic than Confluent Kafka, as well as another solution that is no longer in the market called Xively, which was bought and "buried" by Google. In comparison, these solutions offer way fewer functionalities and respond to other needs.
We found IBM MQ very easy to get started and quick to learn by the new users with a short learning curve and seamlessly integrates with IBM products, and quick to perform self-service analytics and make informed business decisions. IBM MQ is also very straightforward in creating simple and best reports, which are very profitable and productive.
Workday is an incomplete product, by this I mean it must work alongside other products and does not work by itself. Trying to make several different products work smoothly together becomes very challenging. As compared to ADP products, when purchased all together work very well all together. Also, ADP has extensive Training programs and extensive Customer Support. So ADP's products are far superior to Workday's products in my opinion.
Workday has released Financials and is continuing to develop it's Human Capital Management footprint with the addition of Workday Recruiting. I think customers will find that is easy to add on additional functionality in the system. Workday does make it easy for customers to make changes without relying on IT resources. The Business Process framework is a visual tool that allows functional resources to make changes and see the flow of the transaction
Positive: Get a quick and reliable pub/sub model implemented - data across components flows easily.
Positive: it's scalable so we can develop small and scale for real-world scenarios
Negative: it's easy to get into a confusing situation if you are not experienced yet or something strange has happened (rare, but it does). Troubleshooting such situations can take time and effort.
Positive ROI, we were one of the first organizations that went with Workday HCM, and we received numerous discounts. Cloud systems are the way to go and we feel the system is stable for our growing work force.
The user conferences have been helpful to network and learn more deepness in the modules and functionality.
Right off the bat, our implementation costs were lower than budgeted and we had less 'billing' surprises.