In the fast pace online landscape, you need a highly scalable and agile CMS to meet the needs of your customers quickly. Find out how to deploy EPiServer, an enterprise class, multichannel CMS, on the cloud to speed your time to market and deliver customized solutions on the fly.
Peter Yeung, Business Development Director and Peter Sunna, Product Manager of EPiServer
10. Platform today - version 7.1
• Runs in the cloud
• License file tied to IP or MAC
• All frontend servers know about each other
• Files stored on disk (VPP)
• Dependent on local services (Scheduler)
• 1-1 mapping between EPiServer site and IIS site
13. Deployment
• No requirement to install MSI
• No references to Program Files
• No absolute paths
• No Scheduler Service
• No updating web.config on startup
• No server config in web.config
Copy 1 folder to deploy
14. Load balancing
• New Provider Model for ”Remote Events”
• Default is WCF with TCP/UDP
• Amazon provider with zero config
– Amazon Simple Queue Service (SQS)
– Amazon Simple Notification Service (SNS)
15. Files
• New Provider Model
– Blob Provider (Blob = Binary Large Object)
• Default is files on disk
• Provider for Amazon S3
27. The Add-On Store Benefits for Customer
• Get access to latest 3rd Party technologies/functionality
– New Functionality (e.g. translation services)
– New Verticals (e.g. retail PoS integrations)
– New Platforms (e.g Marketing Automation)
• Get access to latest EPiServer functionality
– Google Analytics
– Social Reach
• Auto Updates and Deployments
• Verified and Confidence
• Run your own Enterprise Store