FTP vs SFTP: why plain FTP has no place in modern banking
Both move files. Only one encrypts what travels —credentials included—; and SFTP is not "secure FTP".
Fundamentals
The building blocks of engineering —protocols, encryption, networks, integration and banking— explained with precision and the judgment of someone who runs mission-critical platforms. A maintained knowledge system, not a collection of posts.
Start here What happens when you type a URL and hit Enter?No documents match. Try another term or clear the filters.
Follow the complete journey from entering a URL to receiving a secure application response.
Open the path → Path · Intermediate · 5 documentsUnderstand how enterprise systems connect and why banking integration requires additional controls.
Open the path → Path · Fundamental · 3 documentsWhat each primitive actually protects: encryption, hashing and certificates, and where they get confused in production.
Open the path →Both move files. Only one encrypts what travels —credentials included—; and SFTP is not "secure FTP".
The choreography of systems that runs in under a second: from name to IP, the connection, the request and the render.
How a name becomes an IP, why a change "takes time to propagate", and what you see —and don't— when DNS fails.
Public and private addresses, why many devices share a single public IP, and how the network is segmented to isolate what's critical.
TCP prioritizes ordering, verification and retransmission. UDP cuts coordination when losing or reordering some data beats waiting.
Two families of keys with opposite strengths. Why TLS doesn't pick one, but combines both.
What a certificate is, who signs it, and how the chain of trust that holds up the web is built.
The most common confusion of all. What a hash is, how it differs from encryption, and why it matters for your passwords.
Queues that distribute work and logs that retain and replay events. Why IBM MQ and Kafka get compared so often yet optimize for different models.
The family of standards that moves orders and invoices from one ERP to another with no one typing. Older than APIs, and still moving global trade.
SWIFT doesn't move money: it moves the instruction. How correspondent banking does the rest, and why it's slow and costly.
The standard now replacing SWIFT's MT messages: rich, structured data for payments. The global migration underway right now.
When I publish a new entry or a meaningful revision to the handbook, you get it. No weekly digests, no filler.