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
Salesforce Commerce Cloud
Score 8.0 out of 10
N/A
Salesforce Commerce Cloud (formerly Demandware) is a cloud-based eCommerce solution that touts flexibility and scalability for enterprises. It features merchandising tools, such as sorting, filtering, and image zooming.
$4
per month
Pricing
Apache Kafka
Salesforce Commerce Cloud
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Apache Kafka
Salesforce Commerce 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
—
B2B Commerce:
Starter - $4 price/order
Growth - $6 price/order
Plus - $8 price/order
B2C Commerce:
Starter - 1% Gross Merchandise Value
Growth - 2% Gross Merchandise Value
Plus - 3% Gross Merchandise Value
B2B2C Commerce:
1% Gross Merchandise Value
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.
Global Sites; larger commerce organizations but not too large where the % rev-share would affect its feasibility in a feature comparison. Salesforce is rock solid in infrastructure and rarely has outages or issues; it scaled appropriately for holiday peak and was able to accomplish anything we put our minds to as long as we staffed development appropriately. The latter, however, is not to be overlooked. Developers are necessary and expensive.
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).
Traffic - When we have sales, our traffic will increase exponentially and their cloud can handle the huge uptick in traffic we receive without overloading our servers.
Site updates - it continually monitors in the background for any upgrades or updates needed so we don't have to go in and do it ourselves. A real time saver!
Integration - outside plugins and add-ons are easy to install with Salesforce commerce cloud as it allows a seamless integration of extra plug ins onto our site.
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
The UX within the Business Manager portion of Demandware, the primary interface for marketers, is generally a confusing, inconsistent mess. Particularly infuriating are the lack of consistency for search and sort behavior within the tool.
A number of useful features, such as the ability to set schedules or tie features to unique customer segments, have seemingly arbitrary limitations imposed.
Demandware's idea of leveraging the community to be a learning resource and a sounding board for new ideas and features is a nice theory, but in practice it doesn't work for businesses with a lot of customization. I'm left with the impression that individual support is not a priority.
A huge factor influencing our decision to remain on the Demandware platform is that our new parent company is standardizing all its luxury brands in the US on it. We are fortunate. However, even if we had remained an independent company, I believe we would continue on the Demandware platform for all the reasons outlined in this review. I appreciate the stability the platform has provided to our eCommerce site in the last three years as well as the continuous improvements and technological advances being rolled out that will allow us to keep the site fresh, engaging, modern and stable. I've heard many horror stories from colleagues on other platforms who struggle with the expense and complexity involved with making what should be minor and simple changes and updates to their sites.
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
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.
They are very responsive and a support technician will be assigned quickly. Even if there is further clarification needed for the ticket, or a solution is not immediately available, you feel that someone is there and staying on top of the issue. Most common issues are resolved quickly and satisfactorily.
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.
When I think of Salesforce products, I sometimes think of them interchangeably as one big lump. It's hard not to be incredibly immersed in the ecosystem day in and day out and taking advantage of resources like Trailhead. While Microsoft Dynamics compares in quality and offerings, it doesn't offer the same engagement and resources as Salesforce in its communications, social, and marketing, which makes a difference in terms of relevance and help. Commerce Cloud comes with the support you need to succeed and the tools you need to grow. In a high demand consumer world, we need products like this to keep up and get ahead. The minute we catch up, we're behind. Salesforce helps you stay on pace and create the unique and personalized experiences customers everywhere expect.
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.
