To build a successful microservices application, you need to make many key choices about what technologies and techniques you will use. In this course, Building Microservices, you will learn about several patterns and practices that will enable you to successfully build microservices. First, you will learn about how to structure domain logic and implement a data mapping layer. Next, you will discover the various ways to test microservices. Finally, you will learn how to handle authentication and authorization for communication between microservices. When you are finished with this course, you will have the skills and knowledge to build microservices that are maintainable, testable, and secure.
Mark Heath is a software developer based in Southampton, England, working
for NICE Systems as a software architect creating cloud based digital
evidence management systems for the police. He is the creator of NAudio, an
open source audio framework for .NET.
Course Overview Hi. My name's Mark Heath, and welcome to my course, Building Microservices. I work as a software architect at NICE Systems, where I'm currently helping to create Azure‑based digital evidence management systems for the police. A microservice architecture is an excellent choice when you need to build large, robust applications that can scale, perform well, and adapt quickly to changing business requirements. In this course, we're going to learn about several patterns and practices that will help you to successfully build microservices, and we'll be seeing how these principles are applied by exploring an example eCommerce microservice‑based application. We'll start off by looking at some techniques for structuring domain logic and data access code for our microservices in a way that ensures our code is fast and maintainable. Then we'll look at how we can effectively test our microservices making use of a combination of testing techniques to give us confidence that everything's working as expected. And, finally, we'll look at some of the options for authentication and authorization to ensure that our microservices are properly secured. By the end of this course, you'll be ready to build maintainable, testable, and secure microservices, and identify which patterns and practices are a good fit for each one. The demo application we'll be looking at uses Docker, and although you don't need to have Docker installed, if you do, you'll be able to follow along and try out the demo application for yourself. So I hope you'll join me on this journey to learn about microservices with the Building Microservices course at Pluralsight.