Introduction to Microservices

.NET Angluar Full Stack
Building Microservices with .NET Core 2.0
Microservices
F. BZIOU
Développement Web
Module:

F. BZIOU 2.NET AngularMicroservices
.NET Core 2.0
Microservices
An Introduction to Microservices
Plan
 Origin of microservices
 Discussing microservices
 Understanding the microservice architecture
 Advantages of microservices
 SOA versus microservices
 Understanding the problems with the monolithic architectural style
 Summary

A.Mazoul 3Programmation Mobile
.NET Core 2.0
Microservices
Origin of microservices
“ Microservices is a specialization of and implementation approach for
SOA used to build flexible, independently deployable software systems.”
“ The microservice architectural style is an approach to
developing a single application as a suite of small services, each running in its
own process and communicating with lightweight mechanisms, often an HTTP
resource API. These services are built around business capabilities and
independently deployable by fully automated deployment machinery. There is a
bare minimum of centralized management of these services, which may be
written in different programming languages and use different data storage
technologies.”
F. BZIOU .NET AngularMicroservices

.NET Core 2.0
Microservices
Discussing microservices
 We implement microservices to satisfy business features and implement them with
reduced time to market and greater flexibility.
 Two important architectures that led to its existence:
The monolithic architecture style.
SOA.

.NET Core 2.0
Microservices
Discussing microservices( Monolithic Architecture)
 Large code base: This is a scenario where the code lines outnumber the
comments
by a great margin. As components are interconnected, we will have to bear with a
repetitive code base.
 Too many business modules: This is in regard to modules within the same
system.
 Codebase complexity: This results in a higher chance of code-breaking due to
the fix required in other modules or services.
 Complex code deployment: You may come across minor changes that would
require whole system deployment.
 One module failure affecting the whole system: This is in regard to modules that
depend on each other.
 Scalability: This is required for the entire system and not just the modules in it.
Intermodule dependency: This is due to tight coupling.
 Spiraling development time: This is due to code complexity and
interdependency.
 Inability to easily adapt to a new technology: In this case, the entire system
would need to be upgraded.

.NET Core 2.0
Microservices
Discussing microservices(Service-Oriented Architecture)
“ The main difference between SOA and monolithic is not one or multiple
assemblies. As the service in SOA runs as a separate process, SOA scales better compared
to monolithic.”
What is a service?
It can be a piece of code, program, or software that provides functionality to
other system components.
 This piece of code can interact directly with the database or indirectly through
another service.
It can be consumed by clients directly, where the client may be a website,
desktop app, mobile app, or any other device app.

.NET Core 2.0
Microservices

.NET Core 2.0
Microservices
Reusability: Multiple clients can consume the service. The service can also be simultaneously consumed
by other services. For example, OrderService is consumed by web and mobile clients. Now, OrderService can
also be used by the Reporting Dashboard UI.
Stateless: Services do not persist any state between requests from the client, that is, the service doesn't
know, nor care that the subsequent request has come from the client that has/hasn't made the previous
request.
Contract-based: Interfaces make it technology-agnostic on both sides of implementation and
consumption. It also serves to make it immune to the code updates in the underlying functionality.
Scalability: A system can be scaled up; SOA can be individually clustered with appropriate load balancing.
Upgradation: It is very easy to roll out new functionalities or introduce new versions of the existing
functionality. The system doesn't stop you from keeping multiple versions of the same business
functionality.

.NET Core 2.0
Microservices
Understanding the microservice architecture
“ The microservice architecture is a way to develop a single application
containing a set of smaller services. These services are independent of each other and
run in their own processes. ”
Smaller codebase: Each service is small, and therefore,
easier to develop and deploy as a unit.
Ease of independent environment: With the separation
of services, all developers work independently, deploy
independently, and no one is bothered about any
module dependency.

.NET Core 2.0
Microservices
Understanding the microservice architecture
How does the microservice architecture work?
 It's programming of the modern era, where we are expected to follow all SOLID principles. It's object-
oriented programming (OOP).
 It is the best way is to expose the functionality to other or external components in a way so that any other
programming language will be able to use the functionality without adhering to any specific user interfaces,
that is, services (web services, APIs, rest services, and so on).
 The whole system works as per a type of collaboration that is not interconnected or interdependent.
 Every component is liable for its own responsibilities. In other words, components are responsible for only
one functionality.
 It segregates code with a separation concept, and segregated code is reusable.

.NET Core 2.0
Microservices
Advantages of microservices
 Cost effective to scale
 Clear code boundaries
 Easier code changes
 Easy deployment
 Technology adaptation
 Distributed system

.NET Core 2.0
Microservices
SOA versus microservices
The underlying communication system of SOA inherently suffers from
the following problems:
The fact that a system developed in SOA depends upon its components, which
are interacting with each other. So no matter how hard you try, it is eventually
going to face a bottleneck in the message queue.
Another focal point of SOA is imperative monogramming. With this, we lose
the path to make a unit of code reusable with respect to OOP.

.NET Core 2.0
Microservices
SOA versus microservices :
Prerequisites of the microservice architecture
 Deployment and QA
 A collaboration platform for development
and operations team
 A monitoring framework

.NET Core 2.0
Microservices
Understanding problems with the monolithic architecture style
 Fault tolerance : Monolithic applications have high module interdependency as they are tightly coupled.
 Deployment challenges : any change in the order module would require the entire application to be
deployed again.
“ Scalability of a system is its capability to handle an
increasing/increased load of work. There are two main strategies or types of
scalability in which we can scale our application.”
( Vertical scaling or scale up , Horizontal scaling or scale out )

.NET Core 2.0
Microservices
Important microservices advantages
 Technology independence : we now have the power to use different technologies for each
microservice.
 Interdependency removal : it is easy to add new features, fix bugs, or upgrade technology within
each one. This will have no impact on other microservices.
 Alignment with business goals : respond to business needs and adapt to marketing trends is not a
by-product of microservices, but their goal.
 Cost benefits : Each microservice becomes an investment for the business since it can easily be
consumed by other microservices without having to redo the same code again and again.
 Security : You can have a part of the microservice ecosystem behind firewalls and
another part to user encryption.
…

.NET Core 2.0
Microservices
Summary

F.BZIOU 17.NET AngularMicroservices

Introduction to Microservices

Recommended

Recommended

More Related Content

What's hot

What's hot (8)

Similar to Introduction to Microservices

Similar to Introduction to Microservices (20)

Recently uploaded

Recently uploaded (20)

Introduction to Microservices