No items found.
Last year Sitecore (the company) acquired several API-first, cloud-based products. With these acquisitions Sitecore has been reacting to the trend of Headless CMS (Content Management System) and Content as a Service (CasS). In this blog post, I will lead you through the new and old Sitecore products and then try to speculate the Sitecore product roadmap and how it affects the customer and partner base of Sitecore.
1. Headless CMS:
3. Content as a Service:
Sitecore received a $1.2B investment plan at the beginning of this year, which meant accelerating the growth of Sitecore and expanding the product family. This was realized in acquiring the following companies:
All solutions above are a piece of the current Sitecore Experience Platform product but in the cloud-based world. Let us try to match these products to the existing Sitecore XP platform:
As seen, Sitecore is going on the path to search and acquire well-known and working products instead of developing their own. This perfectly makes sense because these existing products already have a client and partner base or even a community. Not to mention the knowledge these companies already have about the market and how to manage their product type.
Moving to the cloud and entirely using software (or Content) as a service has become a trend in the last few years. By the acquisitions, Sitecore becomes capable of offering different SaaS services together as a "suite" or each of them separately – they follow the same offering approach as with the Sitecore XP/XM products.
Despite moving to the cloud is a trend, it also has many benefits:
The only disadvantage of having the CMS in could is that it's a closed system. There is no chance to "hack" Sitecore if needed as it's possible in Sitecore XP. In an on-premise environment, Sitecore XP is a website that IIS hosts, so you have the chance to over write or extend it at any point.
Using the API-first approach, Sitecore makes easier to plug in different products in the platform by various digital service providers. Theoretically any company can integrate their product into Sitecore by injecting the custom implementations into the correct hooks, what Sitecore provides or will provide.
Sitecore XP will still be there; it won't disappear soon because this was the core product of Sitecore since the beginning – although it had different names in the past years – and most of the existing partners and customers are used to the traditional on-premise product.
Moving a current Sitecore XP implementation to a fully Content as a Service solution needs a complete reimplementation. Therefore, customers can discover other CaaS products, which makes it harder to win the competition for Sitecore. However, Sitecore has a good start in the CaaS world by the acquisitions because they have a lot of domain knowledge and can offer the products together.
I expect some other acquisitions in the future, which could be in the following domains:
Building and integrating the newly acquired products in the Sitecore brand is still in progress. The most mature cloud-based product is Sitecore Content Hub yet, but I am sure the other new products will come soon too.
If you would like to discuss which product would be a perfect fit for you, contact us!
In the modern world, we all like automating repeatable tasks; one of them is the continuous delivery of Sitecore solutions. This post will show you a generic checklist about what to consider when building your Sitecore deployment pipeline for CM and CD servers.
In this article, I will show you a solution for zero-downtime deployment in Azure Kubernetes Service. To add a context for it, first, we are going through some Deployment strategies. Then, I will choose the one that fits our needs. Some of them are supported by Kubernetes natively, some are not (yet). Next, I will outline a System overview by showing you the necessary Kubernetes objects in our AKS. The following part of my article presents our Azure DevOps deployment pipeline to you and briefly goes through the scripts and other settings that do the main thing: zero-downtime deployment. Finally, I am going to Wrap up the things
Agile software development is pretty popular nowadays, but it can be frustrating for people in various roles working on the project. Here are a couple of notes on the experience that we faced on recent projects.