Microservices (en)
0 likes205 views
Microservices are independently deployable components organized around business capabilities with decentralized governance and data. They allow for evolutionary design through infrastructure automation, failure design, and partial deployment. Key advantages include removing integration mess and allowing individual technology choices per service.
More Related Content
![[WSO2Con EU 2017] Implementing Data Exchange Infrastructure in Government](https://cdn.slidesharecdn.com/ss_thumbnails/moldova-final-171107135900-thumbnail.jpg?width=560&fit=bounds)
![[WSO2Con EU 2017] WHO CARES? A WSO2 Cloud Oriented Reference Architecture for...](https://cdn.slidesharecdn.com/ss_thumbnails/61krwlpytgis9fu16mrd-signature-10c352b17e3f171dbc0d45b422788a98081eda1dd1fdd2adacfd28644ef1cf59-poli-171107113845-thumbnail.jpg?width=560&fit=bounds)
![[WSO2Con EU 2017] Extending Your Enterprise Integration Patterns Beyond ESBs](https://cdn.slidesharecdn.com/ss_thumbnails/iqasrssmsvgfykj8m7c6-signature-b0c4715f543dfe5c10349ce8530b5c81ef3fc243f4ed1faea354e2a22502099b-poli-171107112010-thumbnail.jpg?width=560&fit=bounds)
![[WSO2Con EU 2017] Open Interoperability of WSO2 Analytics Platform](https://cdn.slidesharecdn.com/ss_thumbnails/9mrq2xytr5oqokhb1dgt-signature-6abac760590306a9c092f3ba66249d9a805ee6b52c9eb804a80eabb33b95c5ef-poli-171106133401-thumbnail.jpg?width=560&fit=bounds)
![[WSO2Con EU 2017] Creating Composite Services Using Ballerina](https://cdn.slidesharecdn.com/ss_thumbnails/creatingcompositeservicesusingballerinaisuruedited-171108114658-thumbnail.jpg?width=560&fit=bounds)
![[WSO2Con EU 2017] Resilience Patterns with Ballerina](https://cdn.slidesharecdn.com/ss_thumbnails/myteul0aqxm9m9aefn37-signature-25a03a0dd11bea2cb4b5d302614dc9fa369274823e87b86d7bcc419612b27068-poli-171106131830-thumbnail.jpg?width=560&fit=bounds)
Similar to Microservices (en) (20)
Microservices (en)
- 1. Microservices Why do we need them?
- 2. Microservices Main Characteristics By Martin Fowler: 1. Components via services 2. Organized around business capabilities 3. Products not Projects 4. Smart endpoints and dump pipes 5. Decentralized governance 6. Decentralized data management 7. Infrastructure automation 8. Design for failure 9. Evolutionary design
- 3. Grouped by `idea`: 1. Components via services, not libraries 2. Arranging efforts around business needs: ● Some microproducts are being created that rule all the business logic and processes within the service ● Decentralization in product and product storage management 3. Infrastructure: ○ Design for failure ○ Evolutionary design ○ CI & Monitoring Microservices Main Characteristics
- 4. The main idea is to make ... an independently replaceable & independently updatable components b1 b2 b3 a1 c1 c2 d1 d2
- 5. There are 2 main types of components: 1. Libraries (require a new vendor or create your own) 2. Services Types Of Application Components Component a1 b2 Library a1 Service b2 Service
- 6. Monolithic Architecture - tightly coupled application components, all updates cause the whole application code to be deployed, even if there was one one comma missing somewhere (use libraries and/or library-based components) Service Oriented Architecture - gives the ability to replace or update either of application components (use standalone services, mainly via http API) Types Of Applications SOA Microservices
- 7. Organized around business capabilities Monolithic app. / SOA Microservices / SOA Organized around technologies Organized around business capabilities UI Server DBA Payments Marketing CRM
- 8. Microservice Team ● “2 pizza team” rule ● Each team must be as fullstack as possible ● Each team is responsible for all the Microservice processes, starting from the communication with end users and ending by deploying some features to the production environment
- 9. Service Oriented Architecture Service Oriented Architecture (SOA) - a powerful piece of a middleware that will automatically do all the staff (route messages, apply business rules, do filtering, validations and lots of other things). This kind of middleware is also called an ESB (Enterprise Service Bus or, jokingly, Egregious Spaghetti Box). Here a, b, c are the dumb endpoints of certain services. ESB a b c
- 10. Diff SOA Microservices ESB a b c a b c All smartness moves to the end-points ESB becomes just a good piping mechanism Example: Internet The main idea is a Decentralization
- 11. Application Evolution Monolithic application - one hunky big relational database and it commits to all across the application components SOA - lots of services each pulling data from one logically large database Microsevice - each service is responsible for it’s own data and it’s own persistence
- 12. Amazons’ example One of the rules in the Amazon when they shifted to a service oriented architecture is: “One may never talk to another services’ data store, one can only talk to another service through it’s API”
- 13. Microservices Main Advantages 1) it removes the mess with integration of different stuff through a database (even with an ORM support) 2) languages and tools should individually be chosen by a microservice development team Example: individual microservices use a database that make sense for them (one oracle, another one - fancy nosql, another may be mysql, etc)
- 14. Infrastructure automation - Partial application deployment - It’s important to put stuff to live with zero downtime - Blue-Green deployment
- 15. Failover Design - Lots of emphasis on monitoring - Sooner or later remote services gonna fail, particularly if you distribute them between multiple nodes (part of the reason why monitoring is so important) - Tool: Simian Army (Chaos Monkey, Janitor Monkey, Conformity Monkey) - One has to assume the things gonna break
- 16. Resources ● https://www.youtube.com/watch?v=wgdBVIX9ifA ● http://martinfowler.com/articles/microservices.html ● https://github.com/Netflix/SimianArmy/wiki ● http://martinfowler.com/bliki/BlueGreenDeployment.html