Scribd
Upload
38 views16 pages

Microservices Vs Monolithic 13th Jan

The document discusses monolith architectures versus microservice architectures. It provides an agenda covering what a monolith and microservice are, their advantages and disadvantages, communication between microservices, and when to use each approach. Specific topics include vertical versus horizontal scaling, advantages of microservices like technology flexibility and faster deployments, and communication methods between microservices like HTTP, gRPC, and event-driven systems using message queues.

Uploaded by

praj0987shah
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
38 views16 pages

Microservices Vs Monolithic 13th Jan

The document discusses monolith architectures versus microservice architectures. It provides an agenda covering what a monolith and microservice are, their advantages and disadvantages, communication between microservices, and when to use each approach. Specific topics include vertical versus horizontal scaling, advantages of microservices like technology flexibility and faster deployments, and communication methods between microservices like HTTP, gRPC, and event-driven systems using message queues.

Uploaded by

praj0987shah
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 16

Agenda

1 What is a monolith
2 Monolith
Advantages Disadvantages of
3 What is a Microservice

4 a Microservice
Advantages Disadvantages of
5 Communication b w Microservices
6 When to use Monolith vs Microservice

Econ

Rom mence

Productservice Payment
Authentication Logistics
i

User Service

fondest
PHP
Maged
ROR Spree

10 20 orders
Day
Dumais

Fement ET
ip

El
2
1 2000
orderday

Keane
It
Et Fatty

zoo orders

211 Engined

EH Ffg
20
200,000 3
Day serves

pretty a

ax

ng

t
Et
500 000 orders
Day
100 200
Engines

AS
Vertical scaling
if
Ine increased the same
capacity of II
Can't be done
infinitely
Horizontal scaling
to
Add more servers our
Platter
Can be done
infinitely

We aren't the resources


efficiently
utilising
service
Payment
Authservice

Order

Seauchservice
dow Scale
service
Payment Moderate CE
64 cores
High scale
Queenie High 128 GB RAI

scale
Authentication High 2 cores
dess
I.at ttI

selective scaling

Advantages Disadvantages of Men

Advantages
1
Single Deployment
2 121 is
testing easy
3 to
Easy debug
4
Single teams
Disadvantages
A small issue can make
the entire
system day
Tight confling
No tech stack
feasibility
High Deployment time

ideo
service 9PM
streaming
Assignment service HMI
Auth
seei

EI1
t.it
A
MICRO
SERVICES
Instead one app split our
of having only
application into individual components

Each component Microser vin

III
tÉ

One service need to communicate


might
with other services in order to
get
the
med done
Order service

sluice
dormant
Payment service
logistic
yes

Microsfices

I Nw Internet

I FY
FEEL
Order service
onorderplaced1 L

II

t.IE t
I
Advantages Disadvantages of Miseries

Advantages
1 Tech stack
flexibility
2 faster Deployments
3 Selective
scaling
4 new
Easy onboarding of Engines

Disadvantages
lot
of tears
1

2 because
High latency of
Ww Calle
3 B2B
testing
Communication blemicefices
1 HTTP
2
gRPC Protobugs
3 Event Driven Systems

7
NIE

Ter ÉÉ
JSON
f
Java

If id keynote object

name
desc

Easily readable
5850 ect

n
I i
Serialization Deserialization
Marshalling UnMarshalling
Time consuming
2 n
gRPC s

Data developed to make NIN


format
Calls
fate
language agree
y
Communication via protobugs is faster as

No un is
marshalling marshalling required

Event Driven Systems


Asynchnes Id
Seller

logistic

Noting

Inventory
All these services can be called
asynchroney

Queue
Message
Kafka
Rabit Ms
Kafka
honeybees

y.IE

Pusuf odd

You might also like