Building Microservices with . NET Core 2. 0: Transitioning Monolithic Architectures Using Microservices with . NET Core 2. 0 Using C# 7. 0

{"detail":"Not Found"}

Cover -- Title Page -- Copyright -- Credits -- Foreword -- About the Author -- About the Reviewer -- www.PacktPub.com -- Customer Feedback -- Table of Contents -- Preface -- Chapter 1: An Introduction to Microservices -- Origin of microservices -- Discussing microservices -- Monolithic architecture -- Service-Oriented architecture -- What is a service? -- Understanding the microservice architecture -- Messaging in microservices -- Synchronous messaging -- Asynchronous messaging -- Message formats -- Why should we use microservices? -- How does the microservice architecture work? -- Advantages of microservices -- SOA versus microservices -- Prerequisites of the microservice architecture -- Understanding the problems with the monolithic architectural style -- Challenges in standardizing a .NET stack -- Fault tolerance -- Scaling -- Vertical scaling or scale up -- Horizontal scaling or scale out -- Deployment challenges -- Organizational alignment -- Modularity -- Big database -- Prerequisites for microservices -- Functional overview of the application -- Solutions for current challenges -- Handling deployment problems -- Making much better monolithic applications -- Introducing dependency injections -- Database refactoring -- Database sharding and partitioning -- DevOps culture -- Automation -- Testing -- Versioning -- Deployment -- Identifying decomposition candidates within monolithic -- Important microservices advantages -- Technology independence -- Interdependency removal -- Alignment with business goals -- Cost benefits -- Easy scalability -- Security -- Data management -- Integrating monolithic -- Overview of Azure Service Fabric -- Summary -- Chapter 2: Implementing Microservices -- Introduction -- C# 7.0 -- Entity Framework Core -- Visual Studio 2017 -- Microsoft SQLServer -- Size of microservices -- What makes a good service?;Microservices is an architectural style that promotes the development of complex applications as a suite of small services based on business capabilities. This book will help you identify the appropriate service boundaries within the business domain to ensure high cohesion and to define the correct service interfaces to promote loose coupling.