Last updated: May 12 2017
Introduction to DXC Service
Episerver Digital Experience Cloud™ (DXC Service) offers a cloud-first approach to standout engagement including high availability and performance, easy connectivity with other cloud services and existing systems, ability to manage spikes in customer demand, and a platform that is ready to seamlessly adopt the latest technology updates.
Note: This information is intended for developers building solutions based on Episerver DXC Service. Here you will find procedures and guidelines to consider when working with development and deployment.
What is DXC Service?
DXC Service is built on top of other platforms and services, meaning that you as a developer do not need to worry about setting up and configuring the required components.
Episerver DXC Service is based on Microsoft cloud technology, including these components:
- Azure Web Apps
- Azure SQL Database
- Azure Blob Storage
- Azure Service Bus
- Episerver Find
- Content Delivery Network (CDN)
Selecting a package
DXC Service is designed for scalability with consumption-based pricing, and you select a suitable package depending on the number of content items, and whether multiple sites should share the same code base. The included managed services ensure smooth deployment and application availability. See Episerver DXC Service Description for more details.
DXC Service includes a monthly performance report compiling performance metrics benchmarked against previous months. The report includes average page load and response time, page views, events and availability.
How it works
Within DXC Service, Episerver manages complex services such as availability, network configurations and logging, as well as deployment to production. This allows you to focus on development and testing of solutions. As a developer though, you need to be aware of how coding patterns change when running a solution in the cloud.
A solution in DXC Service is based on separated environments for integration/test, preproduction and production, where changes to code and content are deployed between the environments.
Deployment to the Integration and Preproduction environments is done by customer or partner developers, whereas Episerver manages deployment to Production, as part of the service. You can view information about the Integration environment in the Azure portal, and you can use the DXC Service management portal to handle deployments.
See Getting started on how to proceed when you have received the onboarding information from Episerver.