Event-Driven Microservices in Banking and Fraud Detection | Designing Event-Driven Microservices

How do we know whether Event-Driven Microservices are the right solution? This is the question that Tributary Bank faced when they looked at modernizing their old fraud-detection system. They were faced with many challenges, including scalability, reliability, and security. Some members of their team felt that switching to an event-driven microservice architecture would be the magic bullet that would solve all of their problems. But is there any such thing as a magic bullet? Let's take a look at the types of decisions Tributary Bank had to make as they started down this path.

RELATED RESOURCES

CHAPTERS
00:00 - Intro
00:45 - Common problems in a monolithic application
01:59 - Creating isolation in microservices
03:36 - Building resilient microservices
05:49 - Improving the performance of your system
07:39 - Reducing the impact of security breaches
08:59 - Polyglot Architecture
09:56 - Conclusion

--
ABOUT CONFLUENT

#microservices #eventdrivenarchitecture #apachekafka #kafka #confluent

[BlindVirtuoso]

In my opinion coupling is the root of all evil and it can be reduced by building the right logical boundaries across modules.
And if those boundaries are built modules can be easily moved to separate microservices when necessary.

[rvb]

Hi Wade, great job! Thank you for the high-quality video and explanation. I believe you've nailed this topic and use-case. Can't wait to see your next videos. Cheers, Roberto

[hariharanthirumeni]

Microservices are the way to build large and complex systems. Biggest advantage of Microservice architecture is that the isolation of domain.
Isolation makes it loosely coupled, independatly deployable, owns the data and by thus data is encapsulated, independantly scalable and limit the blast radius.
Though the hardware requirement of microservices are exponentially higher than monolith, its worth it. another issue with microservice is the tracebility of transactions in logs. But thats been handled by centralised login framework like zipkin and MDC variables.

[puneetbhatia]

I don’t understand the proposed asynchrony in the fraud detection system with Kafka in the middle. What good is the fraud detection system if it doesn’t stop/prevent fraud on the transaction being serviced? I would have expected it to be synchronous request-response framework. No?

[eugene]

Hey Wade, thanks for a wonderfull video. As a developer if i would start a new project these days i see vertical sliced architecture with endpoints for each slice as a very good candate. Its monolith in a begining but you can decouple it in any point of time. What you think ?

[atehrosius]

Watching this video makes me think hard about how Dapr enables devs build secure and reliable microservices with less friction.

[raptorate]

guys i will save you time, they are not. As much as possible avoid and use simpler solutions, use only when needed or required. Keep solutions lean. The more you know