Book Image

Enterprise Application Architecture with .NET Core

By : Ganesan Senthilvel, Adwait Ullal, Ovais Mehboob Ahmed Khan, Habib Qureshi
Book Image

Enterprise Application Architecture with .NET Core

By: Ganesan Senthilvel, Adwait Ullal, Ovais Mehboob Ahmed Khan, Habib Qureshi

Overview of this book

If you want to design and develop enterprise applications using .NET Core as the development framework and learn about industry-wide best practices and guidelines, then this book is for you. The book starts with a brief introduction to enterprise architecture, which will help you to understand what enterprise architecture is and what the key components are. It will then teach you about the types of patterns and the principles of software development, and explain the various aspects of distributed computing to keep your applications effective and scalable. These chapters act as a catalyst to start the practical implementation, and design and develop applications using different architectural approaches, such as layered architecture, service oriented architecture, microservices and cloud-specific solutions. Gradually, you will learn about the different approaches and models of the Security framework and explore various authentication models and authorization techniques, such as social media-based authentication and safe storage using app secrets. By the end of the book, you will get to know the concepts and usage of the emerging fields, such as DevOps, BigData, architectural practices, and Artificial Intelligence.
Table of Contents (12 chapters)

Microservices architecture definition

In the previous chapter, you learned what is a service, what is business and information modeling, and what is services modeling. All of these concepts and practices apply to microservices architecture as well.

What is microservices architecture?

Microservices architecture is a collection of microservices. A microservice can be defined as follows:

  • The smallest service that does only one thing, that is, Single Responsibility Principle (SRP)
  • It's an independent piece of code and independently manageable without dangling dependencies
  • It's the owner of its own data; no sharing except via services

It is an architectural approach to develop an application (or a system) as a set of small services, where each service works...