Tackling cross-cutting concerns at the front-door

In service-oriented architectures there are several aspects that are shared by all (or most) services. A microservice-based architecture is not an exception, often these are developed in isolation. Cross-cutting concerns are handled by the upper layers of software stacks. An API gateway is one of these layers.
In this Session, Daniel Kocot will discuss:
- The concept of cross-cutting-concerns
- How an API Gateway will support the modernization of legacy by dealing with cross-cutting concerns
- How the implementation of API Gateways can increase the velocity of the development process

Transcript

1. Tackling cross-cutting concerns at the front-door 1
2. codecentric AG Hochstraße 11 42679 Solingen Telefon: +49 (0) 151.10 86 70 74 Daniel Kocot (@dk_1977) Senior Solutions Architect daniel.kocot@codecentric.de www.codecentric.de Innovative - Trustful - Competent - Pragmatic 2
3. Tackling cross-cutting concerns at the front-door 3
5. Architecture 5
6. Patterns 6 Fascade (Gang of Four) API Gateway (Chris Richardson)
7. Cross-cutting concerns 7
8. Definition 8 “Integration of requirements whose implementation is not limited to individual components, but is distributed over many services across the entire system.”
9. 3 Examples 9 Resilience Security Traffic Management - Circuit Breaker - Timeouts - Authorization - Authentication - ACL - Rate Limiting
10. CCC with Kong 10 - extend core functionality with plugins - by service - by route
11. Legacy / Service modernization 11
12. Description 12 - Monolith ⇒ Modulith ⇒ Microservice paradigma - Decoupling
13. Service simplicity GOAL 13
14. Service Development 14
15. Process description
16. Process description
17. Automation GOAL 17
18. DevOps 18
19. Integration of Kong into CI/CD Process 19
20. Thank you! 20
21. References: - Picture Tackle, Navin75, https:/ /flic.kr/p/8oEeF4