alt Hacker NewsMigrating the American express payment network, twice
Comments
unfortunately due to all this A.I noise we are drowning a lot of good things happening in tech specially around DBs
migrating services is easier if your DB supports those things and is more oriented around AP
now a lot of people just jump straight to microservices without considering what their DB can do for them, or if at times they need a relational DB, or if their use case can be served by a hybrid Db.
if you see most of the talks at Monster Scale [0]: They're around DBs
Norton Antivirus for Android doesn't allow me to access the site. Hmm.
NextDNS has blacklisted americanexpress.io as a threat.
> If anomalies were detected
but also
> Latency, throughput, and resiliency characteristics had to remain consistent, and in some cases improve.
> Payment requests could not be dropped, delayed, or left unanswered.
what else would an "anomaly" be?
A fascinating en dash, used as an em dash, followed by two em dashes.
Hmmm.
I wonder what IaC tooling they used. Interesting that “Kubernetes” and “Envoy” are the only product names mentioned that I noticed.
This is cool, but a part of me has to be flip, and humanity is kind of hilarious to me. All of this amazing infrastructure and hard work to essentially just very carefully and accurately subtract one number from another in a way that makes auditing easy.
[dead]
Cmd+F "Kubernetes".
Oh Jesus Christ.
Re: transition to micro services (from monolith).
I’m surprised a network so sensitive to latency (as are payment networks), was able to achieve their latency SLAs with micro services.
Maybe Amex being a closed-loop network helps with latency?