Pretty much all online service APIs (Google APIs, Facebook and so on) out there are text-based.
Granted, JSON formatted text, but still absolutelly human readable text.
The reason for that is because it’s agnostic of the machine architectures (stuff like endianess) on both sides.
The really crazy stuff in banking are the old binary protocols (like EDF) from the time when bandwidth was way less than now (so, the early 90s and earlier).
Many banking systems sync with one another with txt files so… Yeah…
If you think that’s bad, don’t think about how many important communications in the world happen completely verbally.
Pretty much all online service APIs (Google APIs, Facebook and so on) out there are text-based.
Granted, JSON formatted text, but still absolutelly human readable text.
The reason for that is because it’s agnostic of the machine architectures (stuff like endianess) on both sides.
The really crazy stuff in banking are the old binary protocols (like EDF) from the time when bandwidth was way less than now (so, the early 90s and earlier).
O.O
…
What.
(Nobody tell him about the Cobol batch jobs that still run overnight.)
You don’t want to know how bad it is. A good friend is a consultant/business analyst for some salesforce-based loan software. Shit’s terrifying.
SFDC itself is written in Java but uses Javascript-esque APEX for whitelabel development?