Skip to main content

#EventDrivenArchitecture promises scalability, traceability, and resilience—but…

#EventDrivenArchitecture promises scalability, traceability, and resilience—but in a regulated, cloud-native banking environment it also introduces real challenges.

In this #InfoQ video, Chris Tacey-Green explains the key #patterns used to build a real-time payment system in Azure, including inbox patterns, event sourcing, idempotency, and observability.

🎬 Watch now: https://bit.ly/41NZqLe

📄 #transcript included

#SoftwareArchitecture

Preview image for Event-Driven Patterns for Cloud-Native Banking - What Works, What Hurts?

Event-Driven Patterns for Cloud-Native Banking - What Works, What Hurts?

Chris Tacey-Green discusses the shift from synchronous commands to asynchronous events within highly regulated environments. He explains the critical role of Inbox and Outbox patterns in preventing data loss, the nuances of event versioning, and how to maintain decoupling between domains. He shares "battle-tested" principles for implementing fault tolerance and managing eventual consistency.

bit.ly
View original 0 Likes 0 Boosts

Comments (0)

No comments yet.