Book Image

Hands-On Microservices with C# 8 and .NET Core 3 - Third Edition

By : Gaurav Aroraa, Ed Price
Book Image

Hands-On Microservices with C# 8 and .NET Core 3 - Third Edition

By: Gaurav Aroraa, Ed Price

Overview of this book

<p>The microservice architectural style promotes the development of complex applications as a suite of small services based on specific business capabilities. With this book, you'll take a hands-on approach to build microservices and deploy them using ASP .NET Core and Microsoft Azure. </p><p>You'll start by understanding the concept of microservices and their fundamental characteristics. This microservices book will then introduce a real-world app built as a monolith, currently struggling under increased demand and complexity, and guide you in its transition to microservices using the latest features of C# 8 and .NET Core 3. You'll identify service boundaries, split the application into multiple microservices, and define service contracts. You'll also explore how to configure, deploy, and monitor microservices using Docker and Kubernetes, and implement autoscaling in a microservices architecture for enhanced productivity. Once you've got to grips with reactive microservices, you'll discover how keeping your code base simple enables you to focus on what's important rather than on messy asynchronous calls. Finally, you'll delve into various design patterns and best practices for creating enterprise-ready microservice applications. </p><p>By the end of this book, you'll be able to deconstruct a monolith successfully to create well-defined microservices.</p>
Table of Contents (16 chapters)

Chapter 3

What is synchronous and asynchronous communication?

Synchronous communication is where a client makes a request to the remote service (called a service) for specific functionality and waits until it gets a response. Asynchronous communication is where clients make a request to the remote service (called a service) for specific functionality and don't wait, although it does care about the response.

What is an integration pattern?

An integration pattern is where two or more services read and write data out of one data store. 

What is an event-driven pattern and why it is so important for microservices?

In an event-driven pattern, we implement a service in such a way that it publishes an event whenever a service updates its data and another service (dependent service) subscribes to this event. Whenever a dependent service receives an event, it updates its data...