SDL can now run Tridion in their Customer Experience Cloud, here is a short introduction to what we did from a technology perspective

1. SDL CXC & Tridion
Quick Overview
Julian Wraith
October 2014

2. 2
Tridion in the Cloud
Hosted Tridion, fully featured, fully managed.
Implementation follows SDL best practices
Very short time to market (hours rather than days/weeks)
Platform as a Service, not an Infrastructure as a Service.
Vanilla Tridion, but customisations are supported.
Single tenant customer environments, multi tenant management.

3. 3
Design Principles
NoOps  Scalable operations, short time to market
Elasticity  Scale up when needed, scale down when possible
Buy instead of build  Focus on added value
IT Endorsable  Security, resilience, manageability
Pragmatic Portability -> Maintain portability but not at cost of everything.

4. 4
Provisioning architecture
Service Orchestration
Topology Coordination
Server Provisioning
CM Server Pub Server Db Server …
Execution Environment Provisioning
AWS Cloud Resources
Execution Environment
Agnostic
SDL
Tridion

5. 5
Provisioning architecture
Chef
AWS (Cloudformation)
Product
Installers

6. 6
Provisioning flow
1. Provisioning of the infrastructure, security groups, DNS,
tagging and storage
2. Installation of the Tridion application, required modules,
hotfixes and pre-requisites
3. Configuration of the installed software
4. Deployment of the customer’s implementation
5. Hook each infrastructure component to monitoring

7. Global Customer Experience Management
Copyright © 2008-2014 SDL plc. All rights reserved. All company names, brand names, trademarks,
service marks, images and logos are the property of their respective owners.
This presentation and its content are SDL confidential unless otherwise specified, and may not be
copied, used or distributed except as authorised by SDL.