Microservice Architecture

Slim Ouertani

Agenda

● Introduction● Definition● Conclusion

2

Introduction

● Agile● DevOps● Continuous Deployment● Cloud● Design for failure● Containers

3

Common characteristics

● Componentization via Services● Products not Projects.● Smart endpoints and dumb pipes (anti-ESB)● Decentralized Governance● Decentralized Data Management● Infrastructure Automation● Design for failure

4

Monoliths Vs Microservices

5

Default organisation

6

Organized around Business Capabilities

7

Products not Projects● Microservice proponents tend to avoid the project model, preferring

instead the notion that a team should own a product over its full lifetime.

● A common inspiration for this is Amazon's notion of "you build, you run it" where a development team takes full responsibility for the software in production. This brings developers into day-to-day contact with how their software behaves in production and increases contact with their users, as they have to take on at least some of the support burden.

8

Smart endpoints and dumb pipes● The microservice community favours an alternative

approach: smart endpoints and dumb pipes. Applications built from microservices aim to be as decoupled and as cohesive as possible

● Choreographed using simple RESTish protocols rather than complex protocols such as WS-Choreography or BPEL or orchestration by a central tool.

9

Design for failure

● Stateless● Resilience● Event based

10

Evolutionary Design

Smaller, modular services enable more frequent releases and more change overall.

11

Cons

● Operations overhead● Needs of automation● More operations overhead● DevOps Skills and Tech knowledge● Governance and increase in integration

testing

12

Thanks

13

14

Not covered

● Decentralized Governance● Decentralized Data Management● Infrastructure Automation

15