You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: books/Building Event-Driven Microservices/summary.en.md
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -76,6 +76,7 @@ Check Understanding:
76
76
77
77
**Link for More Details**:
78
78
[Ask AI: Integrating Event-Driven Architectures with Existing Systems](https://alisol.ir/?ai=Integrating%20Event-Driven%20Architectures%20with%20Existing%20Systems%7CAdam%20Bellemare%7CBuilding%20Event-Driven%20Microservices)
79
+
79
80
[Personal note: Debezium is solid for CDC, but in 2025 I'd check out newer managed services like those in cloud platforms for easier scaling if ops overhead is a concern.]
80
81
81
82
## Event-Driven Processing Basics
@@ -122,6 +123,7 @@ Check Understanding:
122
123
123
124
**Link for More Details**:
124
125
[Ask AI: Microservices Using Function-as-a-Service](https://alisol.ir/?ai=Microservices%20Using%20Function-as-a-Service%7CAdam%20Bellemare%7CBuilding%20Event-Driven%20Microservices)
126
+
125
127
[Personal note: AWS Lambda and similar are still handy, but in 2025 I'd lean toward more integrated serverless options in clouds for better observability if your stack allows.]
[Personal note: Spark and Flink hold up well, but for lighter workloads in 2025, I might opt for managed serverless streaming to cut down on cluster management.]
0 commit comments