Another fun story from the front lines of TradFi fiat world with KYC/AML...
A bank recently fined millions of dollars for KYC/AML "failures" asks my consulting company to take a look at their SAS Anti-money Laundering application platform because all the performance issues they're having (https://www.sas.com/en_us/software/anti-money-laundering.html)
They have an old, out-dated version (not even the vendor wants to touch it because it's so old) and a newer version (Canada/US).
Leaving aside all the manual steps they have in their process that could be automated (we're talking SPREADSHEETS), they are complaining that when users click on a certain Search button in the UI, for certain cases, it completely locks up the database and makes the app non-functional for all users
Presumably because the query is taking too long and has a read-lock.
My guess is we're talking a least several million records across a few tables, and the query is probably not fully optimized
But then we asked to see hardware specs and their database VM said it had 0.9 CPUs allocated to it
My co-worker and I were utterly confused, see attached convo.
Then I was looking through an old spreadsheet they had of issues with recommendations for fixes, and a cost estimate from internal and external resources. One was for "increasing JVM heap memory" and they had like "estimate of up to two months and $40k"
It's literally just updating a few config files from "1028" to "2046" or whatever, and then restarting the services. Maybe 30 minutes of work.
Incompetence and grift are everywhere.
Peak fiat world with so many things just barely getting by, held together by duct tape and Rube Goldberg processes, with very few people with the WILL and the BALLS to make the hard decision to fix things