4 BIG Software App Challenges For FinServ

on YouTube ↗21m

" summary

Four concrete failure modes and practical mitigations: slow detection and long fixes drive lost transactions so focus on MTTI and MTTR reduction using observability and profilers; run exception-capture inside the CLR like OverOps to get bytecode-level stack and state instead of noisy logs; design for minimal unplanned downtime (example: 25 microservices multiplies availability to ~92–93% so small failures matter) and use canaries, feature flags and fast rollbacks; manage global teams, tribal knowledge and hybrid cloud tracing to avoid hidden integration breaks.

AI-written summary · about

" chapters (7)

1. 0:00Start
2. 0:034 BIG Software App Challenges For FinServ
3. 4:00MTTI & MTTR
4. 8:24Avoiding Downtime
5. 12:13Speed and Stability
6. 14:53Distributed Workforce
7. 19:03Questions?

" related talks

• 28mMaking the Impossible Impossible: Improving Reliability by...Chris Sinjakli · SREcon22 Europe/Middle East/Africa
• 50mTactics and strategies on software development: how to reach ...Otavio Santana · GeeCON 2023
• 48mUnbreakable by Design: The Secret Tech of Antifragile SoftwareIryna Dohndorf · Jfokus 2026
• 47mThe 7 Quests of Resilient Software DesignUwe Friedrichsen · GOTO Berlin 2018
• 29mFrom big to small and back againGus Power · AgileByExample 2016
• 41mFour advanced patterns to improve an application's resiliencePascal Martin · Forum PHP 2025
• 30mThree value inhibiting dysfunctions of enterprise software developmentStefan Holdermans · devopsdays Amsterdam 2023
• 47mLegacy Software: Really a Problem?Eberhard Wolff · Software Architecture Gathering – Digital 2023