Skip to content

Commit 3810db7

Browse files
benjaminhonoriobenjaminhonorio
committed
feat: add EventPro event-driven architecture scenario
Event-driven architecture learning scenario covering SQS, API Gateway, Step Functions, EventBridge, and observability patterns for SAA-C03 prep.
1 parent 2216309 commit 3810db7

10 files changed

Lines changed: 2702 additions & 31 deletions

‎docs/README.md‎

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -79,3 +79,29 @@ flowchart LR
7979
style P5 fill:#e8f5e9,color:#000
8080
style P6 fill:#ffebee,color:#000
8181
```
82+
83+
---
84+
85+
### [EventPro: Tickets Without Crashes](scenarios/eventpro/00-overview.md)
86+
87+
Learn event-driven architecture through the journey of a ticket sales platform that evolves from a
88+
crashing monolith to handling 100K+ concurrent users during flash sales.
89+
90+
**Covers**: SQS, DynamoDB, API Gateway, CloudFront, Step Functions, SNS, EventBridge, X-Ray,
91+
CloudWatch, Lambda
92+
93+
```mermaid
94+
flowchart LR
95+
P1["Phase 1<br>Monolith"] --> P2["Phase 2<br>SQS"]
96+
P2 --> P3["Phase 3<br>API GW"]
97+
P3 --> P4["Phase 4<br>Step Fn"]
98+
P4 --> P5["Phase 5<br>Events"]
99+
P5 --> P6["Phase 6<br>Observe"]
100+
101+
style P1 fill:#ffcdd2,color:#000
102+
style P2 fill:#fff9c4,color:#000
103+
style P3 fill:#fff9c4,color:#000
104+
style P4 fill:#c8e6c9,color:#000
105+
style P5 fill:#c8e6c9,color:#000
106+
style P6 fill:#bbdefb,color:#000
107+
```

‎docs/_sidebar.md‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,3 +24,11 @@
2424
- [Phase 4: Logging & Monitoring](scenarios/medvault/phases/phase-4-logging-monitoring.md)
2525
- [Phase 5: Multi-Account Strategy](scenarios/medvault/phases/phase-5-multi-account.md)
2626
- [Phase 6: Threat Detection](scenarios/medvault/phases/phase-6-threat-detection.md)
27+
- **EventPro Event-Driven Scenario**
28+
- [Overview](scenarios/eventpro/00-overview.md)
29+
- [Phase 1: The Crashing Monolith](scenarios/eventpro/phases/phase-1-crashing-monolith.md)
30+
- [Phase 2: SQS Traffic Absorption](scenarios/eventpro/phases/phase-2-sqs-traffic-absorption.md)
31+
- [Phase 3: API Gateway Protection](scenarios/eventpro/phases/phase-3-api-gateway-protection.md)
32+
- [Phase 4: Step Functions Workflows](scenarios/eventpro/phases/phase-4-step-functions-workflows.md)
33+
- [Phase 5: EventBridge Routing](scenarios/eventpro/phases/phase-5-eventbridge-routing.md)
34+
- [Phase 6: Event-Driven Observability](scenarios/eventpro/phases/phase-6-observability.md)

‎docs/exam-coverage.md‎

Lines changed: 42 additions & 31 deletions
Large diffs are not rendered by default.

‎docs/scenarios/eventpro/00-overview.md‎

Lines changed: 84 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,84 @@
1+
# Tickets Without Crashes: The EventPro Story
2+
3+
## The Business
4+
5+
You're the Lead Architect at **EventPro** - a ticket sales platform for concerts, sporting events,
6+
and theater. The company has grown to 500K users, but faces a critical problem: **flash crowds**.
7+
8+
When 50,000+ fans try to buy tickets simultaneously (like a Taylor Swift concert sale), the system
9+
collapses under the load. This isn't just a technical problem - it's a business crisis.
10+
11+
## The Trigger
12+
13+
> "We sold Taylor Swift tickets last month. 50,000 fans hit 'Buy' at 10:00 AM. Our API crashed in 30
14+
> seconds. We oversold 200 tickets and had to refund furious customers. The CEO is asking why our
15+
> competitors handle this and we can't."
16+
>
17+
> — CTO, post-incident review
18+
19+
## Learning Objectives
20+
21+
This scenario teaches event-driven architecture and asynchronous processing patterns for
22+
high-traffic applications:
23+
24+
- [**Phase 1**: The Crashing Monolith](scenarios/eventpro/phases/phase-1-crashing-monolith.md) -
25+
Understanding the problem
26+
- [**Phase 2**: SQS Traffic Absorption](scenarios/eventpro/phases/phase-2-sqs-traffic-absorption.md) -
27+
Queues and decoupling
28+
- [**Phase 3**: API Gateway Protection](scenarios/eventpro/phases/phase-3-api-gateway-protection.md) -
29+
Rate limiting and caching
30+
- [**Phase 4**: Step Functions Workflows](scenarios/eventpro/phases/phase-4-step-functions-workflows.md) -
31+
Orchestration and Saga pattern
32+
- [**Phase 5**: EventBridge Routing](scenarios/eventpro/phases/phase-5-eventbridge-routing.md) -
33+
Event-driven integration
34+
- [**Phase 6**: Event-Driven Observability](scenarios/eventpro/phases/phase-6-observability.md) -
35+
Tracing and monitoring
36+
37+
## Architecture Evolution Map
38+
39+
```mermaid
40+
flowchart LR
41+
P1["Phase 1<br>Monolith<br>Problem"] --> P2["Phase 2<br>SQS<br>Queuing"]
42+
P2 --> P3["Phase 3<br>API GW<br>Protection"]
43+
P3 --> P4["Phase 4<br>Step Fn<br>Workflows"]
44+
P4 --> P5["Phase 5<br>EventBridge<br>Routing"]
45+
P5 --> P6["Phase 6<br>X-Ray<br>Observable"]
46+
47+
style P1 fill:#ffcdd2,color:#000
48+
style P2 fill:#fff9c4,color:#000
49+
style P3 fill:#fff9c4,color:#000
50+
style P4 fill:#c8e6c9,color:#000
51+
style P5 fill:#c8e6c9,color:#000
52+
style P6 fill:#bbdefb,color:#000
53+
linkStyle default stroke:#000,stroke-width:2px
54+
```
55+
56+
## AWS Services Covered
57+
58+
| Phase | Primary Services | Key Concepts |
59+
| ----- | ------------------------- | ----------------------------------------- |
60+
| 1 | - | Race conditions, synchronous bottleneck |
61+
| 2 | SQS, DynamoDB | Queue decoupling, DLQ, conditional writes |
62+
| 3 | API Gateway, CloudFront | Throttling, usage plans, caching |
63+
| 4 | Step Functions, SNS | Saga pattern, workflow orchestration |
64+
| 5 | EventBridge | Event routing, fan-out, scheduling |
65+
| 6 | X-Ray, CloudWatch, Lambda | Distributed tracing, observability |
66+
67+
## SAA Exam Domain Mapping
68+
69+
This scenario primarily covers:
70+
71+
- **Domain 2 (Resilient)**: Decoupling, fault tolerance, Saga pattern
72+
- **Domain 3 (High-Performing)**: Traffic absorption, caching, async processing
73+
- **Domain 1 (Secure)**: API protection, rate limiting, DDoS mitigation
74+
75+
## How to Use This Guide
76+
77+
Each phase includes:
78+
79+
1. **Business Context** - What's happening with EventPro
80+
2. **Architecture Decision** - What we're building and WHY
81+
3. **Key Concepts** - SAA exam-relevant knowledge with verified numbers
82+
4. **Diagrams** - Visual representation of the architecture
83+
5. **Cross-References** - Links to related content in other scenarios
84+
6. **Exam Tips** - Key points for the SAA certification

0 commit comments

Comments
 (0)