Microservices architecture
Download as PPTX, PDF0 likes206 views
The document discusses microservices architecture as a modernized version of service-oriented architecture (SOA), emphasizing its advantages such as speed of delivery, scalability, and modularity. It highlights principles like statelessness, high observability, and the importance of automation, while also noting potential drawbacks such as increased complexity and challenges with consistency in distributed systems. The conclusion states that the microservices architecture, while beneficial for growth and scalability, introduces significant complexity compared to traditional monolithic systems.
Microservices architecture
- 3. This is not new! The old new thing...
- 4. SOA service oriented architecture • Modernized version of SOA New world: • Speed of delivery • Scalability • Cloud / devops
- 6. PRESENTATION LAYER BUSINESS LOGIC LAYER DATABASE LAYER A monolith Module A Module B Module c Module D
- 8. PRESENTATION LAYER BUSINESS LOGIC LAYER DATABASE LAYER microservices API API BUSINESS LOGIC LAYER DATABASE LAYER consume Produce Microservice 1 Microservice 2
- 9. Modularity Autonomous hide implementation details Stateless highly observable principles
- 10. Modularity (TEAM) UI - team Dba - team SERVER UI dba SERVER dbaUI dba SERVER UI SERVER - team monolith microservices
- 11. autonomous
- 14. stateless (1) (2) A stateless server is a server that treats each request as an independent transaction that is unrelated to any previous request
- 19. Modularity Autonomous hide implementation details Automation Stateless highly observable principles
- 20. Advantages
- 21. Polyglot architecture - The right technology for the job - reduce technical debt
- 22. Evolutionary design - Remove - Add - Replace - Experimental microservice
- 23. Selective scalability Nb users > 500
- 24. Big vs small Smaller code base Simpler to develop / test / deploy / scale Start faster Easier for new developers
- 25. drawbacks
- 26. • Distributed system - Consistency - Request travelling • Slow (http) • Multiple databases • Integration tests Conclusion: • The Microservices architecture is more complex Than a monolith. • This is the cost of growing and scaling easily
- 29. Service discovery server I want TO TALK TO THE PRODUCT SERVICE ! Here is the product service ! Service discovery
- 30. Service discovery (load balancing) Service discovery server I want TO TALK TO THE PRODUCT SERVICE ! Here is one instance of product service !
- 31. Api Gateway API Gateway Browser UI e.g. angular 2 Mobile app
- 32. THANKS !
Editor's Notes
- #3: The term "Microservice Architecture" has sprung up over the last few years to describe a particular way of designing software applications as suites of independently deployable services. While there is no precise definition of this architectural style, there are certain common characteristics around organization around business capability, automated deployment, intelligence in the endpoints, and decentralized control of languages and data.
- #6: in software engineering, a monolithic application describes a single-tiered software application in which the user interface and data access code are combined into a single program from a single platform
- #13: EAR: All above files (.jar and .war) are packaged as JAR file with .ear (enterprise archive) extension and deployed into Application Server. A WAR (Web Archive) is a module that gets loaded into a Web container of a Java Application Server. Basically EAR files are a superset containing WAR files and JAR files.
- #15: Easier to scale / recover from failure
- #27: Transactions: Increased Processing overhead – It costs many messages to be shared between sites to complete a distributed transaction.
- #32: API gateway Insulates the clients from how the application is partitioned into microservices insulate the clients from the problem of determining the locations of service instances Provides the optimal API for each client Reduces the number of requests / roundtrips. Backend for front end