Deliver more rapidly to accelerate digital experience success with new features — from container infrastructure orchestration to integrated data and marketing functionality.
If you want a quick overview of the whole release, check out Sitecore 10 highlightsarticle. In the following article, we’re going to drill down into the changes and benefits for the technical teams of developers, DevOps professionals, and IT staff.
Take a tour!
In this video, Nick Wesselman provides a quick tour for developers of the new stuff in Sitecore 10:
First announced as supported in Sitecore 9.3, Sitecore 10 brings about new tools from Sitecore on how to adopt a container approach in your delivery flow. Why are containers important? In general, if you’ve been doing your development with virtual machines or local installations, moving to a Docker-driven development and infrastructure flow will be a huge benefits for you. In general, you can address four major areas:
Do you need to secure 14 signatures and present technical documentation just to run a script on your production database? Does it take a group of enterprise architects to approve a change to your application? Or do you have no restrictions whatsoever but are so afraid of touching the production server in case the slightest change brings everything down?
You are not alone… the word ‘Production’ has become synonymous with ‘Hallowed’ and a culture of fear dominates all changes made to a working production environment. An upcoming production deployment can feel like the Big Bad Wolf is coming to blow your house down.
It is very fashionable to apply a single word to pretty much ANYTHING to try to get in on the latest trend. The current ‘Whatever-Ops’ trend (MarketingOps, ChatOps, OpsOps) is one such example. For a while, though, we’ve been having the word ‘Continuous’ thrown in front of a whole lot of activities in the software development world: Continuous Delivery, Continuous Improvement, Continuous Management. There’s a reason for this… repeatable processes are a key ingredient to predictable delivery. And predictable delivery means money in the bank!
I am a big fan of continuous delivery and deployment. You might have seen me write about it a few timesbefore. When I first bring the idea up with clients, there is hesitation. One might even call it fear. The benefits are huge, allowing you to reap the return on investment immediately, but the big question is “how”. How does an organization switch to a continuous delivery model?