2. Microservices
● Microservice architecture is a type of service-oriented
architecture in which an application is organised as a series of
loosely connected services.
● Microservices architecture is characterised by fine-grained
services and lightweight protocols.
● Communication through the well defined API’s
● This is a separate Business logic instead of one Problem
statement
6. Advantages
● Greater agility
● Faster time to market
● Better scalability
● Faster development cycles (easier deployment and debugging)
● Easier to create a Cl/CD pipeline for single-responsibility
services
● Isolated services have better fault Tolerance
● Platform- and language agnostic services
● Cloud-readiness
7. In summary
● Microservices may be deployed individually, giving teams more
control.
● Microservices are scalable in their own right.
● Microservices decrease downtime by isolating faults.
● The smaller codebase allows teams to grasp the code more
quickly, making it easier to maintain.
8. Cons
● More collaboration is required (each team has to cover the
whole microservice lifecycle)
● Because of the architecture's complexity, it's more difficult to test
and monitor.
● Due to the requirement for microservices to communicate,
performance will suffer (network latency,message processing,
etc.)
● It's more difficult to keep the network up to date (has less fault
tolerance, needs more load balancing, etc.)
● Doesn't function until there's a strong company culture in place
(DevOps culture,automation practices,etc.)
● Concerns about security (harder to maintain transaction safety,
distributed communication goes wrong more likely,etc.)
12. Container are very light weight
SERVER
HOST OS
GUEST OS
HYPERVISOR
LIBRARIES/Bin
APP A
GUEST OS
LIBRARIES/Bin
APP B
VM
SERVER
HOST OS
APP A APP B
LIBRARIES LIBRARIES
CONTAINER
S
• Containers are isolated but share OS
• Increase the compute density and
memory utilization
DOCKER ENGINE
