Moving a customer to DD4T (with Azure with OData and Elastic Search)

Moving a customer to DD4T (with Azure with OData and Elastic Search)

How not to move your SDL Tridion implementation to the cloud After seven years using SDL Tridion, Yale School of Medicine recently transitioned their on premise Content Delivery stack to a cloud based installation on Azure with DD4T and OData. This presentation covers the ‘lessons learned’ with respect to development process, architecture, performance and cost. Key topics include: • Why we moved to the cloud • Limitations of transitioning an on premise SDL Tridion license to the cloud • How we structured the team and project • Pros and Cons of the OData Provider for DD4T • Azure Cloud Architecture (Web Apps, Virtual Machines, Databases, Traffic Managers and CDN) • Comparisons to SDL’s Cloud based offering • How we would do things differently if we did it again This session will be led by Chris Summers, a 5 time SDL Tridion MVP and 15 year Tridion veteran. Joining Chris will be Justin Fansler, the project lead and Director of Operations at the Yale School of Medicine Web Group and Mark Albis, the Web Systems Development Manager and in-house owner of the SDL Tridion platform at Yale School of Medicine.