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
Tableau Cloud
Score 8.0 out of 10
N/A
Tableau Cloud (formerly Tableau Online) is a self-service analytics platform that is fully hosted in the cloud. Tableau Cloud enables users to publish dashboards and invite colleagues to explore hidden opportunities with interactive visualizations and accurate data, from any browser or mobile device.
$15
per month per user
Pricing
Apache Kafka
Tableau Cloud
Editions & Modules
No answers on this topic
Tableau Viewer
$15
per month billed annually per user
Enterprise Viewer
$35
per month billed annually per user
Tableau Explorer
$42
per month billed annually per user
Enterprise Explorer
$70
per month billed annually per user
Tableau Creator
$75
per month billed annually per user
Enterprise Creator
$115
per month billed annually per user
Tableau+
Contact Sales
Offerings
Pricing Offerings
Apache Kafka
Tableau Cloud
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Apache Kafka
Tableau Cloud
Features
Apache Kafka
Tableau Cloud
BI Standard Reporting
Comparison of BI Standard Reporting features of Product A and Product B
Apache Kafka
-
Ratings
Tableau Cloud
7.6
74 Ratings
7% below category average
Pixel Perfect reports
00 Ratings
7.756 Ratings
Customizable dashboards
00 Ratings
8.774 Ratings
Report Formatting Templates
00 Ratings
6.563 Ratings
Ad-hoc Reporting
Comparison of Ad-hoc Reporting features of Product A and Product B
Apache Kafka
-
Ratings
Tableau Cloud
7.6
74 Ratings
6% below category average
Drill-down analysis
00 Ratings
8.674 Ratings
Formatting capabilities
00 Ratings
7.271 Ratings
Integration with R or other statistical packages
00 Ratings
6.247 Ratings
Report sharing and collaboration
00 Ratings
8.672 Ratings
Report Output and Scheduling
Comparison of Report Output and Scheduling features of Product A and Product B
Apache Kafka
-
Ratings
Tableau Cloud
7.8
72 Ratings
5% below category average
Publish to Web
00 Ratings
8.568 Ratings
Publish to PDF
00 Ratings
7.567 Ratings
Report Versioning
00 Ratings
7.655 Ratings
Report Delivery Scheduling
00 Ratings
8.559 Ratings
Delivery to Remote Servers
00 Ratings
6.538 Ratings
Data Discovery and Visualization
Comparison of Data Discovery and Visualization features of Product A and Product B
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.
If you're using Tableau as the primary BI tool, then Tableau Cloud is well suited to publish and share the results with a wide(r) audience. It is well suited for various degrees of self-service proficiency, from pure consumers of analytical work to more advanced users who can use web editing for smaller or larger adjustments, and even for desktop power users who will publish their work to Tableau Cloud. It has many good ways to organize the content and make it easily accessible via search, favorites, folders, collections ("playlists for your data"), or history ("recents"). It might not be ideally suited if there are many on-prem sources to be used (even though there are options to connect them) or if you have very special requirements regarding custom server setup, which is limited in a shared cloud environment like Tableau Cloud.
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).
Tableau Online is completely cloud based and that's why the reports and dashboards are accessible even on the go. One doesn't always need to access the office laptop to access the reports.
The visualizations are interactive and one can quickly change the level at which they want to view the information. For example, one person might be more interested in looking at the country level performances rather than client level. This is intuitive and one doesn't need to create multiple reports for the same.
The feature to ask questions in plain vanilla English language is great and helpful. For quick adhoc fact checks one can simply type what they are looking for and the Natural Language Programming algorithms under the hood parse the query, interpret it and then fetch the results accordingly in a visual form.
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
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
Based on comments from our clients, I awarded it this grade. Non-technical customers frequently compliment us on the ease with which they can utilize Tableau Online. Usability is rarely a source of contention amongst our customers. Few complaints have come from me as a user of our internal products.
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.
I have not had any issues that require customer support from Tableau at this time, which speaks well to Tableau. I have taken an online course with Tableau and it was very professional and well done, so based on that I would assume a similar level of quality for their customer service.
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.
In determining whether to go with Tableau Online versus Alteryx, two important factors stood out in determining our go-to solution. First, while Alteryx is an impressive tool for data cleansing, it did not stack up in terms of data visualization capabilities. Tableau, on the other hand, provided us everything we needed in terms of visualizing our data and analytics. The second factor is cost. Well neither solution would be considered cheap, Tableau was the more cost effective solution for our needs.
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.