Azure Kubernetes Services with Microservices : Understanding Its Patterns and Architecture

Design and implement scalable microservices using Azure Kubernetes Services (AKS) and other Azure Services. This book will help you understand why and when to choose microservices as a solution for modernization and how to use Azure DevOps to implement CI/CD for deploying microservices. The book starts with an introduction to the evolution to microservices and AKS along with its components. You will learn design patterns to implement microservices on AKS and understand Kubernetes as a container orchestration platform. You will go through the common errors faced in AKS-based applications and ways to handle them. You will learn error handling tips and tricks and how to design for business continuity and disaster recovery. The book discusses things you should know related to security and monitoring when working with AKS-based applications. The book presents a practical approach to set up processes for CI/CD, such as building Build and release pipelines for AKS deployment using Azure DevOps. After reading this book, you will understand design considerations for designing scalable microservices and know how to implement the design through AKS. What You Will Learn Know design patterns for microservices and how to handle failure scenarios Be aware of architecture and design considerations Understand container and Kubernetes architecture components Understand security and monitoring aspects Take a practical approach to continuous integration and continuous delivery Who This Book Is For IT professionals associated with cloud computing, especially with Microsoft Azure Table of Contents About the Authors About the Technical Reviewer Acknowledgments Chapter 1: Introduction to Microservices and AKS Introduction The History of Distributed Computing Client Server Model Component Technology Web Services Service Oriented Architecture What Are Microservices? Monoliths vs. Microservices Introduction to the Cloud-Native Architecture How Business Benefits from Cloud-Native Applications An Introduction to AKS and its Components Container Images The Cluster The Control Plane Deploying Apps and Workloads Summary Appendix Chapter 2: Microservices: Architecting and Design Considerations Introduction Microservice Architecture Benefits Deriving Business Value Defining a Goal-Oriented, Layered Approach Modularity Cohesiveness Interrelationships Maturity Model for Microservice Architecture Goals and Benefits Applying the Goal-Oriented, Layered Approach Microservices Design The Systems Approach to Microservices Service Solution Process and Tools Organization Culture Embracing Change Standardization and Coordination Standardizing Process Standardizing Outputs Standardizing People Standardization Trade-Offs A Microservices Design Process Set Optimization Goals Development Principles Sketch the System Design Implement, Observe, and Adjust The Microservices System Designer Goals and Principles Goals for the Microservices Way Reduce Costs Increase Release Speed Improve Resilience Enable Visibility Trade-Offs Operating Principles Netflix Antifragility Immutability Separation of Concerns UNIX Suggested Principles Do One Thing Well Build Afresh Expect Output to Become Input Don’t Insist on Interactive Input Try Early Don’t Hesitate to Throw It Away Toolmaking Platforms Shared Capabilities Hardware Services Source Code Management, Test, and Deployment Data Storage Service Orchestration Security and Identity Architectural Policy Localized Capabilities Culture Aligning Your Teams Fostering Innovation Summary Appendix Chapter 3: Microservices Design Patterns Introduction Service Design Microservice Boundaries Microservice Boundaries and Domain-Driven Design It’s Only a Model Bounded Context Smaller Is Better Ubiquitous Language API Design for Microservices Message-Oriented Hypermedia-Driven Data and Microservices Shipping Company Example Event Sourcing System Model for Shipping Company CQRS Distributed Transactions and Sagas Asynchronous Message-Passing and Microservices Dealing with Dependencies Pragmatic Mobility System Design and Operations Independent Deployability Do You Need More Servers? Microservice Architecture Is a Product of Its Time Docker and Microservices The Role of Service Discovery The Need for an API Gateway Security Transformation and Orchestration Routing Monitoring and Alerting Summary Appendix Chapter 4: Containers and Azure Kubernetes Services Introduction Containers How Containers Solve This Problem How Containerization Is Different from Virtualization Using Docker Installing Docker Desktop in Your Development Environment Exploring the docker run Command Running a Webserver Viewing the Contents of the Web Page from the Terminal Cleanup Processes The Dockerfile Use Entrypoint to Make the Greeter a Bit More Configurable Use COPY to Launch a Simple Static Website Monitoring Docker Containers and Docker Logs Docker Exec: Run Commands Inside a Running Container! Docker Inspect Creating a Docker Hub Account and Connecting to It Tagging and Pushing Your Image to the Registry Using Kubernetes Kubernetes Tooling and Setup Summary Appendix Chapter 5: Securing and Monitoring Applications Running on AKS Introduction Security Concepts Master Security Node Security Cluster Upgrades Network Security Kubernetes Secrets Azure Kubernetes Service Checklist Security Concepts: Conclusion Monitoring Concepts Container Insights Azure Monitor Features Summary Chapter 6: CI/CD for AKS Introduction A Quick Look at DevOps Goals of This Exercise Creating Azure Kubernetes Service Using Azure Portal Creating Azure Container Instance Using Azure Portal Working with Visual Studio to Build the Sample Application CI/CD with Azure DevOps Summary Index Trademarked names, logos, and images may appear in this book. Rather than use a trademark symbol with every occurrence of a trademarked name, logo, or image we use the names, logos, and images only in an editorial fashion and to the benefit of the trademark owner, with no intention of infringement of the trademark.The use in this publication of trade names, trademarks, service marks, and similar terms, even if they are not identified as such, is not to be taken as an expression of opinion as to whether or not they are subject to proprietary rights.