Apache Kafka vs Yellowfin

• Apache Kafka is able to handle a large number of I/Os (writes) using 3-4 cheap servers.
• It scales very well over large workloads and can handle extreme-scale deployments (eg. Linkedin with 300 billion user events each day).
• The same Kafka setup can be used as a messaging bus, storage system or a log aggregator making it easy to maintain as one system feeding multiple applications.

Read full review

• Presentation of information for executive reporting.
• Collaboration and action task assignment on pinpointed issues highlighted in reports and dashboards.
• End client easy self - service reporting.

Read full review

• Still a bit inmature, some clients have required recoding in the last few versions
• New feaures coming very fast, several upgrades a year may be required
• Not many commercial companies provide support

Read full review

• Initially the Yellowfin business model was difficult to align to the VSV model but through some simple negotiations a workable model was reach which made in commercial application viable
• Some additional licensing models could also be of value as we do not use the product in a pure business intelligence only application.

Read full review

• Positive impact on ROI since now we can use one large deployment of Apache Kafka that can be used for multiple scenarios ( storage systems, log aggregate, messaging queue ).
• It is open-source so there are no licenses or subscription fees reducing the cost of deployment.
• Data can now be ingested and analyzed in real-time making it easy to fine-tune the customer experience and decision making for internal IT.

Read full review