Using Event Driven Architecture to Transform Core Banking -- Matthew Lancaster

แชร์
ฝัง
  • เผยแพร่เมื่อ 31 พ.ค. 2024
  • Matt pulled us out of the tech stack for a second to focus on what's beneath it, the foundational layer of the application pyramid: business drivers. This, he says, is what will turn everyone event-driven. Non-tech companies, even in old-school industries like banking, are increasingly becoming tech-centric.
    Matt's been working with core banking at Accenture for a while, and it comes with lots of legacy challenges. You can't just wipe everything clean and start over in a greenfield project, you have to respect and learn to integrate with legacy systems, some of which are well over a decade old.
    He's got some practical advice from his own forays into bringing banks into the future.
    More about Emit Conference: www.emitconference.com
    More about Serverless: www.serverless.com
  • วิทยาศาสตร์และเทคโนโลยี

ความคิดเห็น • 6

  • @rajchoudhary4349
    @rajchoudhary4349 2 ปีที่แล้ว +1

    Awesome narration..!! Soothing to ears... didn't missed a word..!!

  • @ericjones485
    @ericjones485 4 ปีที่แล้ว +10

    Looks like 4 people that watched this are mainframe sales people

  • @aishwarya1993
    @aishwarya1993 4 ปีที่แล้ว

    As someone who works in a similar space of migrating systems for the health insurance enterprises, I appreciate the details and great presentation on what you did Matt!

  • @nesaluj
    @nesaluj หลายเดือนก่อน

    This was brilliant Matt! You talked about anything and everything that the industries are stuggling with - with their Tech adoption and modernization. And how they can refer to some of the patterns that have stood the tests of the time, embrace thoughtful gradual adoption and wake up into brighter mornings! And possibly in the process lead into more invvovations 🙂

  • @aatifnazar8203
    @aatifnazar8203 3 ปีที่แล้ว +1

    thats a TON of insight

  • @velo1337
    @velo1337 2 ปีที่แล้ว

    tldr create a second database, implement to read/write to the legacy system and the new db, build new io streams into the new system, implement new features ontop of the new io streams