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
SAP Commerce Cloud
Score 8.2 out of 10
N/A
SAP Commerce Cloud (formerly Hybris) is designed to help businesses sell more goods, services, and digital content through every touchpoint, channel, and device through their multichannel ecommerce and order management solution, available as a SaaS or on-premise.
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.
SAP Commerce Cloud is well-suited for large enterprises requiring robust personalization, seamless multi-channel integration, and the ability to handle high-volume transactions, especially during peak periods like Black Friday. Its scalability and advanced features make it ideal for businesses needing to manage complex product catalogs and global operations.Enough development capacities are needed to have a best in class shop
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).
Centralized Data Management: SAP Commerce Cloud excels in centralizing data from various operational sectors, which is pivotal in the chemicals industry. This feature allows for better oversight and management of complex supply chains, regulatory compliance, and customer interactions. Having a single source of truth for crucial business data minimizes discrepancies and promotes informed decision-making.
Real-Time Data Processing: The real-time data processing capability of SAP Commerce Cloud is invaluable. It aids in timely adherence to regulatory changes and helps in meeting customer demands promptly. In a sector where regulations and market conditions are ever-evolving, real-time data processing is fundamental for maintaining compliance and ensuring customer satisfaction.
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
It's a little pricey; further cost reductions will expand product selection; also, trained operators are required.
HAC occasionally functions extremely slowly and does not provide any problem messages; it simply gets stuck. Logging into the Backoffice for testing purposes causes a lot of trouble; it does not enable us to log in in one attempt, and the page refreshes every time we enter in the credentials.
SAP Commerce and Spartacus together becomes one of the omnichannel powerhouse of commerce application. It also comes with edge advantage with out of the box integrations with many SAP applications and also non-SAP applciations which gives it edge advantage over other tools. The main reason being the integration becomes easier as SAP shares the common data schema and model across all its product line and new feature releases are compatible with all the SAP product line.
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
More true headless and a more rationale pricing. Since moving from the Hzbris Monolyth towards SAP Commerce Cloud a lot of progress has been made, but dissecting the monolyth into composable components where you just pay for what you use is still a longer journey and here pricing should be more realistic. Things become so expensive once they have the SAP stamp on them (example the SAP CIAM)
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.
We have the right to open a ticket or submit request to SAP support teams for all the problems we have experienced. They also provide solutions for critical issues within 48 hours. In addition, the product has support documents such as a user guide and admin guide. In addition, there is a strong community of users. In this way, we can access solution of some specific problems that we have fallen on from there.
Scalability of the product was good Seamless integrations were helped in reducing the implementation for the development team to integrate with the SAP ERP Product framework helped customer to customize and adapt the new features which were developed basis business processes and ease of customer experience. Deployment and creation of the build becomes very easy with the CCv2 setup.
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.
SAP Cloud is much better than GoDaddy. it was a smooth transition and every aspect of the program is easier. My scalability increased greatly from GoDaddy to SAp Commerce Cloud and sales are now tracked easier and inventory is at the touch of a button, making sales much easier than previous software.
The business users/admins were able to quickly segment products by brand, allowing for unique branding and header-less page design. As new products are added to the SAP backend, all characteristics and pricing automatically migrate to Commerce Cloud. We also segment our user sign-on (domains) by brand and allow targeting displays.
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.
It has a positive impact on my client's business and ROI is higher than expected. As orders count is increasing due to smooth and better experience.
My current client's customers have given very positive experience about new website built on SAP Commerce Cloud.
Due to SAP Commerce Cloud website rollout is very easy and due to it, my current client has introduced around 25 websites. As SAP Commerce Cloud logic needs to develop once and can be reused for multiple websites easily with minimal effort.
Branding is also very easy as promotions, events can be implemented on the website easily and with minimum time.
SAP Commerce has helped our client to integrate the Recommendation tool ISS which is easy to configure after this tool product sale is increased. The best thing was that integration was very easy and quick.
One option of Blue/Green deployment helping us to check the production release in advance on production environment. Prev we don't have this option and many times face P1 issue in prod which had ruined client reputation. But now this feature is helping lot
