Microservices – also known as Microservice architecture – is an “service-oriented architecture composed of loosely coupled elements that have bounded contexts”.

1. Micro Services : The Journey So Far
and Challenges Ahead

2. Contents
• Microservices
• Microservices and Service-Oriented Architecture
• Microservice Evolution
• Why microservice
• Microservices vs. Monolithic
• Microservice Architecture
• Characteristics
• Benefits
• Challenges
• Advantages and Disadvantages
• Future Scope

3. What is MicroServices
• Microservices – also known as Microservice
architecture – is an “service-oriented
architecture composed of loosely coupled
elements that have bounded contexts”.

4. Microservices and Service-Oriented
Architecture
• Independent services .
• Microservices are similar to service-oriented
architecture.
• SOA depends on products such as enterprise
service buses heavyweight middleware.
• Microservices depend only on lightweight
technologies.

5. Microservice Evolution
• The term “microservices” was first discussed
at a May 2011 software architecture workshop
• Microservices are evolved from both the
technological and architectural perspectives.

6. The Technological Perspective

7. The Architectural Perspective

8. Why Microservices?
• A monolithic application is built as one single
unit.
• A monolithic application consists of:
i. Client side interface
ii. Database
iii. Server side logic.

9. Monolithic vs Microservices

10. Microservices
• Lightweight and portable.
• RAM and CPU resources.

11. Microservice Architecture

12. Characteristics of Microservices
• Multiple Components
• Built For Business
• Simple Routing
• Decentralized
• Failure Resistant
• Evolutionary.

13. Microservices Benefits
• Faster development.
• Easier testing.
• Simplified deployment.
• Fault isolation .
• Greater scalability.
• More technology choice.

14. Microservice Challenges
• Building Microservices
• Testing
• Versioning
• Deploying
• Logging
• Monitoring
• Debugging
• Connectivity.

15. Advantages
• Freedom to independently develop.
• It can be developed by a small team
• Code.
• Easy to understand.
• Starts the web container more quickly.

16. Disadvantages
• Complicated and tedious.
• Developers have to put additional effort.
• The architecture results in increased memory
consumption.
• Additional complexity.
• Number of services increases, managing
whole products will become complicated.

17. Future Scope
• Preferred style of developers.
• Microservices aim to resolve segmentation
and communication problems.