Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Building Microservices with .NET Core 2.0
  • Toc
  • feedback
Building Microservices with .NET Core 2.0

Building Microservices with .NET Core 2.0

By : Gaurav Aroraa
3.2 (15)
close
Building Microservices with .NET Core 2.0

Building Microservices with .NET Core 2.0

3.2 (15)
By: Gaurav Aroraa

Overview of this book

The microservices architectural style 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 your business. We'll start by looking at what microservices are and their main characteristics. Moving forward, you will be introduced to real-life application scenarios; after assessing the current issues, we will begin the journey of transforming this application by splitting it into a suite of microservices using C# 7.0 with .NET Core 2.0. You will identify service boundaries, split the application into multiple microservices, and define service contracts. You will find out how to configure, deploy, and monitor microservices, and configure scaling to allow the application to quickly adapt to increased demand in the future. With an introduction to reactive microservices, you’ll strategically gain further value to keep your code base simple, focusing on what is more important rather than on messy asynchronous calls.
Table of Contents (11 chapters)
close

Isolation requirements for microservice deployment

In 2012, Adam Wiggins, co-founder of the Heroku platform, presented 12 basic principles. These principles talk about defining new modern web applications from an idea to deployment. This set of principles is now known as the 12-factor app. These principles paved the way for new architectural styles, which evolved into microservice architectures. One of the principles of the 12-factor app was as follows:

"Execute the app as one or more stateless processes"
- Adam Wiggins (https://12factor.net/)

So, services will be essentially stateless (except the database, which acts as the state store). The shared nothing principle is also applied across the entire spectrum of patterns and practices. This is nothing more than the isolation of components in order to achieve scale and agility.

In the microservice world, this principle...

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech
bookmark search playlist font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete