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

Monolithic application deployment challenges

Monolithic applications are applications where all of the database and business logic is tied together and packaged as a single system. Since, in general, monolithic applications are deployed as a single package, deployments are somewhat simple but painful due to the following reasons:

  • Deployment and release as a single concept: There is no differentiation between deploying build artifacts and actually making features available to the end user. More often, releases are coupled to their environment. This increases the risk of deploying new features.
  • All or nothing deployment: All or nothing deployment increases the risk of application downtime and failure. In the case of rollbacks, teams fail to deliver expected new features and hotfixes or service packs have to be released to deliver the right kind of functionality.
A Hotfix, also...

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