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 Experience Manager
Score 8.0 out of 10
N/A
Sitecore Experience Manager is an enterprise-grade CMS competing with Oracle WebCenter, IBM Web Content Manager and Adobe. It presents a fairly wide and comprehensive swath of inbuilt features. In Sitecore WCM editing takes place from within the page with its inline editor, allowing editors and authors to create display rules and content within the context of the page in an integrated process. It allows the creation of blogs, wikis, polls, integrates with social media, and is mobile…
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.
Great for companies that are looking to create customized, tailored content solutions and be willing to put in the hard work and effort to maximize the value out of the tool. If your company is just looking for very basic content management without all the bells and whistles, I'd recommend looking elsewhere for less [money].
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).
Personalisation of advertising banners based upon knowledge of the customer, like location or previous searches enables us to target customers with products and offers that they are more likely to engage with, which has been done to good effect.
The use of Sitecore for content management enables the business and design team to perform changes to things, like images, content and page structure, which would otherwise have required a code release, which is costly in terms of man power.
The A/B testing in Sitecore is good because it allows us to statistically verify minor changes to the site - like advert changes or component ordering on the page - as to whether or not they positively impact conversion.
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
Sitecore is Customer Engagement Platform. It comes with lots of features (e.g. Authoring, Analytics, personalization, A/B Test, Webforms for marketers etc), But, most of them are not being used by many clients. If you are really looking for just CMS (only authoring and publishing), then I don't think Sitecore is a way to go.
You need to have a strong Sitecore certified developer base to manage the Sitecore platform (if you are using all features). It's the same case with others. But, finding a Sitecore certified (costs $$) developer is tough in the market. Now the market is growing (thanks to Sitecore promotional events) and Sitecore is gaining popularity, It may be easy to find such developers in the future. If you want to leverage most out of the Sitecore community you need to be a Sitecore certified developer.
Sitecore comes with lots of built-in features and marketplace components. I feel this puts in a little tricky situation. It gives an opportunity for a normal developer to use some of the free marketplace module, which may or may not be supported in a future version of Sitecore. which may put the entire platform in risk to upgrade to latest Sitecore version. You need to have a proper process to control and validate the marketplace components before using them.
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
With any platform that offers so much capability, usability will naturally be more challenging. Sitecore does an admirable job and made massive strides in version 8, but at some times offers too many ways to achieve the same task allows users to sometimes take a path less efficient than the preferred path.
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.
Sitecore Support is very knowledgeable and helpful. We have raised a number of issues with them and they rarely fail to come up with an acceptable solution.
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.
The decision to select Sitecore was not ultimately mine, but the fact that we were able to leverage in-house Microsoft .Net (C#) experience on a platform that had a library of extensions, but also allowed us to customize and keep private our confidential IP has been a big help. When you see a SharePoint site or a Drupal site you can usually tell "oh this is a MS SharePoint site", but with Sitecore the ability to customize and have different views even different components based on device type makes Sitecore a clear winner.
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.
ROI depends so much on implementation. Its would be difficult to comment in a positive or negative regarding CMS product to direct ROI. A non-technical user would be surprised at what a basic installation of Sitecore looks like. "Hello World" comes to mind. With that in mind we can look at two things, Sitecore Support and Sitecore Partners.
Certified Internal Developers and Sitecore Support: This depends on the qualifications of your existing departments regarding implementing a enterprise CMS. No experience to some experience, this is a no brainer, rigorously vet top and middle partners and hire one to lead this effort. If your experienced still hire a partner and vet them but hire a middle to small partner and have them help, not lead.
"Sitecore Window": You could equate Sitecore in some implementation as throwing expensive parts at a car problem. If your business requirements and data consumption needs are not within this cost window then in the end on paper it will be difficult to see ROI or that there just wasn't a return. Then it will be time to look at other lower cost alternatives The initial cost is just the start. Over engineering and expensive horizontal integration partners can cost someone a promotion or job.
If your content workflows are complex, sites rendering data requirements are large and performance and scalability are paramount. Sitecore should be in your top 3.
