Hello and welcome to the Dotnet Monolithic to Microservices Migration learning path presented to you by Cloud Academy. 

In this course, we'll introduce you to the learning path contents, intended audience, learning objectives, and prerequisites. Before we start I would like to quickly introduce myself. My name is Jeremy Cook, I'm one of trainers here at Cloud Academy, specializing in Dev-Ops. Feel free to connect either with myself, or the wider team here at Cloud Academy, regarding anything presented within this learning path. You can email us at support@cloudacademy.com. 

The Dotnet Monolithic to Microservices migration learning path consists predominantly of hands-on coding and refactoring demonstrations. 

Together with introductory instructional course-ware, hands-on labs where you get to practice with related technologies, and an exam to assess your required knowledge of the subject matter. The Dotnet Monolithic to Microservices Migration consists of two individual courses that walk you through an architectural migration a of sample e-commerce store. The e-commerce store starts off as a Windows 2008 IIS hosted ASP.Net Monolithic application, as it would have been likely active 10 year ago. This version of the e-commerce store is referred throughout the courses as the Store2008 version. We then proceed by reacting the Store2008 version, into it's modern form, known as the Store2018 version. The updated Store2018 version will be refactored and implemented as a microservices based application. 

Additionally, as we go about updating and modernizing our e-commerce store, we'll move away from a vendor centric solution, and leverage a more open-sourced mindset. Using technology such as Docker, Dotnet Core, Lennox and more. With an emphasis on ensuring portability of our modernized Store2018 application amongst popular cloud-container runtimes such as Amazon ECS using Fargate, and Amazon EKS, we will open up and expose our backend e-commerce stylise, as Restway EPI inpoints, maximizing the ability for future integrations. We'll examine different front end HTMR rendering techniques, updating our design from a service-side rendered approach to a cloudside rendered approach using the popular react framework. 

The intended audience for this learning path includes: software developers and architects, DevOps practitioners interested in CICD implementation, anyone interested in understanding and adopting microservices and Restway API's within their own organization, anyone interested in modernizing an existing application, those interested dockering containers in general, and those interested in container organization run-times, such as Kubernetes.

By completing this path you will, understand the principles and patterns associated with microservices, understand the principles and patterns associated with Restful Api's, understand important requirements to consider when migrating a monolithic application into a microservices architecture, understand the benefits of using microservices and associated software patterns and tools to build microservice based applications at speed and scale, understand the trade-offs between different architectural approaches, become familiar and comfortable with modern open-sourced technologies such as Dotnet Core framework, Docker, Docker componants, Lennox, Terraform, Swagger, and React, become familiar with dockering container orchestration run-times to host and run containers such as Docker Compose, Amazon ECS using Fargate and Amazon EKS. 

The following prerequisites will be both useful and helpful for this learning path, a basic understanding of software development, a basic understanding of the software development life-cycle, a basic understanding of Dev-Ops and CIDC practices, familiarity with Dotnet in C#, and finally, familiarity with the AWS platform.

Okay, the learning path introduction has now been completed. Go ahead and close this lecture and we'll see you shortly in the first course.