Sitecore Symposium 2017: Incredible Scale Sitecore Implementation

This session was lead by Simon Jones, Glen McInnis, Bart Plasmeijer, and Jaspar van den Bosch from Valtech. They talked about how they manage 1,000 websites in 100 countries and 50 languages across 15 brands for a popular makeup brand. Here are my notes from the session:

  • Principals for success
    • Reuse, reuse, reuse
    • Build for scale
    • Quality is non-negotiable
    • Automation is your friend
    • Share knowledge among teams
    • Have a single global delivery model
  • Azure
    • Use azure services
      • Redis cache
      • Azure search
      • App insights
  • Sitecore
    • Follow helix guidelines for the backend as well as the frontend
    • Componentize everything
      • Maintain a component library that are versioned
      • Create components as nuget packages
        • Easier to share among multiple projects
        • Can create a package that contains multiple commonly used components
  • DevOps Principals
    • Automate everything
    • Fail early, recover fast
    • Keep it simple
  • How to do this at scale
    • Zero downtime deployments
    • Ability to test in PROD without being live
    • Devs can access real-time log data
    • Solid and fast QA process
  • Automated standards
    • Treat infrastructure as code and test
    • Automate and monitor critical processes
  • Updating Sitecore
    • Because everything is nuget packages, you can test the package against the target version of Sitecore
    • Update the code as needed, then update the nuget package
  • Interesting Observations
    • They have over 60 server instances for all of their content
      • Can be managed and upgraded indepenantly
      • Each instance has only one brand
      • Each brand has more than one instance
      • Each instance has multiple languages
    • They do not have one massive multi-tenant Sitecore instance
      • The database would be massive and very slow

Find the rest of my notes from Sitecore Symposium 2017

Leave a Reply

Your email address will not be published. Required fields are marked *