The document discusses cloud-native architecture, emphasizing its benefits such as speed, agility, and innovation. It highlights key concepts such as event-driven architecture, microservices, and decentralized governance while outlining the importance of loose coupling and command query responsibility segregation (CQRS). It also underscores the role of API-first development and consumer-driven contract tests in cloud-native environments.

1. Cloud-Native
Architecture

2. Architecture

3. Cloud-Native Development
Event-Driven Architecture
API First / CDCT
Cloud-native

4. Cloud-Native Development

5. Why?
Cloud-native

6. New Economics
Speed
Agility And Innovation

7. How?
Cloud-native

8. Performance Elasticity
Resilience Security

9. Ok … Enough with the marketing!
How?
Cloud-native

10. Microservices
Cloud-native

11. Small
Smart Endpoints / Dumb Pipes
Decentralized Governance
Decentralized Data Management
Design For Failure
Automation

12. Development
Source code
 JAR File
 Docker Image
 OpenShift Pod

13. Key to cloud-native success?
Cloud-native

14. Loose coupling
Cloud-native

15. Event-Driven Architecture

16. CQRS
Command Query Responsibility Segregation
Synchronous Asynchronous
80 %

17. Pareto Principle

18. What is an event?
Something that has happened in the past.
Types of data
An event can
contain 3 types of
data
data it owns
data it needs
reference data

19. Example
Cloud-native > Event-Driven Architecture

20. Event-Driven Synchronized Repository

21. API First / CDCT

22. API Guidelines
Cloud-native > API

23. Cloud-native > Consumer Driven Contract Tests