On the path to evolutionary architecture with APIs

Transcript

1. On the path to evolutionary architecture with APIs 1
2. codecentric AG Hoher Wall 15 44137 Dortmund Telefon: +49 (0) 151. 10 86 70 74 Daniel Kocot Head of API Experience & Operations daniel.kocot@codecentric.de www.codecentric.de Innovative - Trustful - Competent - Pragmatic 2 https://linktr.ee/danielkocot
3. Evolutionary architecture?
4. An evolutionary software architecture supports guided, incremental change across multiple dimensions. Rebecca Parsons and Neil Ford
5. Guided Change 5
6. Incremental Change 6
7. Technical 7 Data Security Operational / System Multiple Architectural Dimensions
8. Guidance
9. An API should not be strictly coupled to the architecture of the backend
10. When the API delivers the right datasets at the right time the consumers are not interested in the architecture of the API backend.
11. Evolve your architecture without breaking any API contract
12. Preliminary work
13. API Interaction Patterns Hypermedia Query Event-Based Tunnel Resource
14. Classification of API Type Platform APIs Service APIs
15. Platform APIs • Use a framework the development team is proficient with • To create a first representation of the data • Transformation is maybe needed
16. Service APIs 16 API as a Product Transformations Aggregations • Use Enterprise Integration Patterns • Apache Camel, Spring Integration, Apache Nifi, SaaS Service (e.g., Make), ... • Use again a framework the development team is proficient with • To create aggregated or composed representation of data from Platform APIs • These APIs help to create a better experience for the user
17. Building architectures
18. But…Stop!
19. We need an abstraction layer
20. Because we like to think directly in technology
21. We should talk about patterns
22. Patterns for Abstraction
23. Facade / Adapter Strangler Fig API Layer Pattern Composable Type of Patterns to be considered
24. 24 Facade / Adapter
25. 25 Strangler Fig
26. 26 API Layer
27. Combining Patterns with API Types
28. 28 Combination Thinking Service APIs Platform APIs
29. But how do Gateways or Proxy fit to the topic of architecture?
30. Mixing infrastructure with architecture
31. “Implement an API gateway that is the single-entry point for all clients. The API gateway handles requests in one of two ways. Some requests are simply proxied/routed to the appropriate service. It handles other requests by fanning out to multiple services.” Chris Richardson 31
34. Misconception and Misunderstanding
35. Gateway vs. Proxy 35
36. 36 Service Proxys
37. Little helper
38. Proxying and Routing Look for Service Proxies 38
40. Cross-Cutting Concerns 40 Traffic Management Security Resilience
41. Take the right decision(s) at the right time
42. And please don’t start your initiative from the point of a gateway or proxy
43. Wrap Up
44. API Architecture gets more and more complex over time 44
45. Working with abstractions and layers 45
46. Choose things wisely 46
47. Tools don’t drive the needed architecture 47
48. Further information • https://linktr.ee/danielkocot • codecentric blog • Article-Series IT Spektrum 48
49. Q&A 49
50. Thank you! 50
51. 51 References Cover Slide: Photo by Matt Duncan on Unsplash Slide 2: Photo by Danist Soh on Unsplash Slide 7: Photo by Daniil Silantev on Unsplash Slide 11: Photo by Tim Gouw on Unsplash Slide 17: Photo by Randy Fath on Unsplash Slide 18: Photo by Joshua Hoehne on Unsplash Slide 22: Photo by Omar Flores on Unsplash Slide 35: Photo by Aaron Burden on Unsplash
52. codecentric AG Hoher Wall 15 44137 Dortmund Telefon: +49 (0) 151. 10 86 70 74 Daniel Kocot Head of API Experience & Operations daniel.kocot@codecentric.de www.codecentric.de Innovative - Trustful - Competent - Pragmatic 52 https://linktr.ee/danielkocot