[IT Days Cluj 2016] Deliver Efficient RESTful APIs for Microservice Architectures

We look at the pros and cons of using microservice architectures, showcase RESTful approach for critical operations, discuss how to describe them with behaviour-driven tests, and tackle performance concerns.

Transcript

1. Georgiana Gligor Architecture Consultant @ Tekkie Consulting Deliver Efficient RESTful APIs for Microservice Architectures
2. Georgiana Gligor • Geek. Mother. Do-er. • Large-Scale Application Architect • PHP Cluj Meetup Organiser • Systems Engineering PhD Student @gbtekkie gb@tekkie.ro
3. Monolith Microservices
4. Martin Fowler 2014 Microservice Architectures
5. Monolith
6. Scale
7. Microservices
8. Scale
9. Characteristics
10. 1. Componentization via Services + independently deployable + explicit component interface - remote calls more expensive
11. 2. Organized around Business Capabilities Cross-functional teams.
12. 3. Products not Projects
13. 4. Smart endpoints and dumb pipes ‣ Microservice • holds its own domain logic • acts like a Unix filter ‣ Communication achieved using: • REST • lightweight message bus
14. 5. Decentralized Governance Use the right tool for the job.
15. 6. Decentralized Data Management
16. 7. Infrastructure Automation
17. 8. Design for failure Strong emphasis on failure handling.
19. 9. Evolutionary Design Components that can be independently upgraded / replaced entirely.
20. RESTful Approach
21. REST • REpresentational State Transfer • architectural style, not a protocol • introduced by Roy Fielding in 2000
22. REST Confusions Roy’s thoughts from 2006 in the Yahoo discussion group.
23. REST Constraints • start with an empty set of constraints • client-server for separation of concerns • stateless • response must be labelled as (non)cacheable
24. REST Constraints (Cont’d) • uniform interface between components • layered system: a component can only “see” its immediate layer • code-on-demand [optional]
25. Efficiency
26. REST process view adaptation of fig 5-10
27. How Do I Make It Efficient? • Infrastructure as code. • Establish non-functional requirements early on. • Measure all the things! • Don’t let code rot.
28. Broken Windows Theory
29. Resources • Roy Fielding dissertation • REST architectural style discussion list • Broken Windows Theory
30. Image Credits • Spock • Broken Window • Shrek & Godfather • Martin Fowler