Daivagna Nanavati

   Hi Team, At Horizontal Digital , we as a team decided to create set of webinars and online sessions for developers to help learn new concepts of "Sitecore 10" offerings. As a part of that, different team mates started preparing for Sitecore 10 new features so those information can provided to the team and they can all push and learn SC10 in much better way and those topics can help them in their certifications too   As a part of those different webinars, I took the topic on "Sitecore Content Serialization (SCS)" In SC10 certification one (out of many) competency is " Content serialization ", We all have been working in TDS, Unicorn tools to serialize the content and use it to share, deploy sitecore content, but with SC10 there is a new way of serializing content. Basically there are two ways which we can use SCS 1) Sitecore CLI : Is a dotnet core based command line interface, we can install nuget modules on top of this for SCS and we can start using

  Hi Team, Today i am going to share one of the nightmarish issue with you all, We are having Sitecore 9.1.1 hosted in azure PaaS environment Our site was working just fine and no noise, but we have been working on a feature release where 7-8 months of development needed to be released to production, Big GO LIVE event right?  Also to make the development smoother we also introduced BLUE/GREEN deployment slots in the same release, so we can easily SWAP slots and go live Everything went well, we went live, we even did load and performance testing on our staging and pre-prod and we were confident enough of results Very next day we started getting "SITE DOWN" alerts, and also product owners and clients mentioned that site is very slow for them in US time and in our morning when we were accessing it, it was working lighting fast so we were clue less at start, but we started digging  1) First thing caught our eyes were HIGH CPU spikes, in US time, also without any traffic CPU used