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
Sitecore Digital Experience Platform
Score 8.9 out of 10
N/A
The Sitecore Experience Platform (Sitecore XP) is a digital experience platform used to build websites and create customer experiences online. The solution boasts fast content authoring, built-in personalization features, testing and other optimizations, as well as analytics and marketing features.
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.
Sitecore offers Content Hub with Product Content Management and Content Management Platform. The Digital Experience Platform and Content Hub can both host structured content and publish the finalized version to Experience Edge. Both platforms offer different ways to manage content. During a technical and business evaluation, the evaluation panel must understand the difference between a Content Modelling focused approach, or a layout management focused approach. Sitecore Digital Experience Platform is also best not to be used to host many files and images in the Media Library. That responsibility should be offloaded to a digital asset management company like Sitecore Content Hub DAM. The technology evaluation panel must also understand how to work with a Headless CMS, where the HEAD needs to be hosted, and the costs associated with the HEAD. Composable DXP is fantastic, but everyone must understand the various cost components. Marketers and the data team will need to go into the CDP and Personalize the platform with an excellent understanding of how a composable "installation" works. All the Martech vendors have similar challenges that data and development teams need to work through with a full experience. Any CDP/analytics platform will, at some stage, require further data enrichment from other sources. Understanding the Sitecore Search features and limitations is also essential.
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).
Comprehensive Solution: Sitecore offers a fully integrated suite of products that cover the full spectrum of DXP capabilities, including search, personalization experimentation and more, delivering a complete composable DXP solution for customers.
Beyond Headless: XM Cloud provides more than just headless capabilities, featuring in-built tools like authoring host, page editor, etc., enabling faster and more powerful implementations.
Focus on AI: Sitecore has now got an excellent AI offering called Stream; it looks promising; however, it would be too early to give feedback on the same.
Customization: Sitecore's backend is highly customizable, allowing for deep modifications through pipelines and patch configurations.
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
Experience Editor is a little old fashioned and sometimes slow to use.
Bulk operations in the Content Editor
Sitecore serialization is should be part of the Content Editor to provide visual reference for items which are serialized and will be overwritten by future deployments similar to what Unicorn does so well
Sitecore has proven that it can deliver on its promise of a robust, reliable enterprise CMS solution with plenty of features. Also, they keep updating it with more and better features. Now that we are highly trained on it we have started on getting the most out of it and we plan to keep doing more of that in the future.
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
We use Sitecore extensively because it provides a single platform for managing content, personalization, and digital experiences across multiple web properties and customer journeys. At our scale, the biggest value is consistency, governance, and the ability for marketing teams to manage experiences without needing engineering support for every change. It also integrates well with the broader CRM/marketing stack, so it becomes quite embedded once deployed.
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.
1. Customized software development & maintenance. 2. Technology Consulting - Consulting-based services for technology solutions data engineering or cloud solutions. 3. Used for tapping into multiple data sources such as CRM and marketing automation systems and, creating automated data extracts with a high-end visual representation of data. 4. Implemented for scheduling an existing report to automatically refresh and be delivered to specific users at a specific regular interval.
Sitecore captures and remembers every single interaction your customers and prospects have in any part of the system, allowing you to build comprehensive, ever-learning profiles of each individual. From email marketing, to social media, to online shopping, Sitecore remembers where each interaction left off so you can automatically continue the conversation. Sitecore helps you manage your content for each and every experience your customers enjoy. Customize what content you want and the system will take care of how it's displayed.
Make sure you work with a partner that can help you take advantage of the entire platform. Specifically we see a lot of customers not taking advantage of Sitecore DMS and thus missing a huge opportunity. Sitecore is a platform that is meant to be constantly optimized and improved upon.
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.
Really the only comparable product to Sitecore DXP is Adobe Experience Manager. Both are very well established and robust content management platforms. Products like Contentful and Contentstack are very lightweight and do not have as many built-in features like DXP, so it is not a fair comparison. For highly complex enterprise type engagements, Sitecore DXP and AEM are always brought to the table together for consideration.
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.
Since moving the site to Sitecore we have had an increase in conversion - that's the ultimate goal of all these things. It's likely to be partly tied in to the re-design that happened at the same time, but the way in which you can personalise and change things really helps give the best customer journey.
The negative impact we've seen is mainly due to expectations around how easily things can be shared between separate instances of Sitecore - if you haven't built stuff sharable it won't be sharable, but the business have been sold Sitecore (partly) on the basis that things would be easily sharable.
My developers don't all like working in Sitecore - it takes time to learn, takes a long time to build and run as well as requiring a few processes around it, like Unicorn Sync, etc. One of my devs has actually asked to not work on it again! So, a potential recruitment issue.
