Apple Filing Protocol will soon disappear completely from macOS
Apple Filing Protocol is one of Apple's original file-sharing technologies. Its client software will soon be gone from macOS forever.

Apple has deprecated support for Apple Filing Protocol in macOS Sequoia 15.5.
The year after Apple released the Macintosh in 1984, it introduced a proprietary networking standard called Apple Filing Protocol. Part of a suite of software which included AppleTalk, AppleShare, and Apple cabling hardware called LocalTalk, AFP allowed users to share files across Macs on local area networks.
This was a decade before the Internet and its open protocols became popular in the mid-1990s.
Apple developed AFP in part because the original Mac OS and most Mac software used another proprietary technology called resource forks. Most early Mac software files contained two forks: a data fork and a resource fork containing user interface and other elements.
The problem was that if you copied early Mac software uncompressed across non-Mac computers, the destination computer would strip the resource forks off files, damaging them.
Apple later developed an additional collaboration and sharing environment called Apple Open Collaboration Environment (AOCE) and PowerTalk, both of which were failures. AOCE was introduced in Mac OS 7.1.1 but didn't gain any real traction until Mac OS 8.5 when it was upgraded.

The macOS Keychain was originally part of Apple's PowerTalk software.
When the internet was commercialized in the mid-1990s, Apple abandoned AOCE in favor of internet standards such as TCP/IP. Apple also sold a separate server product in a box called AppleShare Server, which Matt Fuller has some spectacular photos of on his site.
A late version of AppleShare packaged as a standalone product was released called AppleShare IP, which allowed AFP to run over TCP/IP networks.
AppleShare volumes and disk volumes shared from users' Macs were accessed through an original Mac software component called Chooser. Later versions of the Chooser allowed direct IP connection to servers by clicking a button and specifying an IP address.
The now-defunct Mac OS X Server product also included AFP, SMB/CIFS, and NFS File Services as part of its file-sharing features. Apple even sold a preconfigured PowerPC-based G4 "server" Mac, which had AppleShare IP preloaded.

The original Mac OS Chooser with the AppleShare icon selected.
AFP in Mac OS X and macOS
Apple released Mac OS X in the year 2000. Mac OS X included support for AFP and AppleShare until OS X 10.9 (Mavericks) when Apple switched the default file sharing protocol in macOS to Microsoft's Server Message Block (SMB).
Apple removed the ability to run an AFP server in macOS 11 (Big Sur). However, users can still use the AFP client in the Finder in macOS via the Go->Connect to Server menu item and the afp:// protocol to connect.
When you connect to an AFP volume in the macOS Finder, the connected shared volume(s) mount on your Desktop just like local disk volumes.
Early 2000s Macs included a Mac OS 9 emulator called Classic, which also enabled users to continue using OS 9 and connecting to and from OS X Macs using AFP:

Apple deprecates support for AFP in macOS Sequoia 15.5
macOS Sequoia 15.5 has deprecated AFP, effectively preparing to end support for AFP clients at some point in the future. Apple has signaled in the enterprise release notes for macOS Sequoia 15.1 that it will be "removed in a future version of macOS," without stating exactly when that will occur.
As such, you should transition all your file-sharing and networking workflows to SMB. For older UNIX-only servers that still support NFS, that protocol can still be used as well.
There's an NFS app for macOS called NFS Manager from Germany's Marcel Bresink.
On pre-15.5 Macs, see the Terminal AFP command mount_afp
by opening Terminal and typing:man mount_afp
and pressing Return on your keyboard. To exit the man system, press Control-Z or the q key.
Several third-party NAS vendors, such as Synology and others, include AFP support in their products, but that's likely to come to an end soon too. You'll probably have to use SMB to connect to these.

AppleShare IP 6 retail user guide.
Third-party solutions
For those users who absolutely need to hang on to AFP, an open third-party product called Netatalk is available and is still being maintained as of 2025. How long Netatalk will be able to support AFP remains to be seen however, since it too is based on the protocol itself.
Since Apple removed native core AFP support from macOS, even third-party AFP products may no longer work.
If you're still running an older Mac OS 7, 8, or 9.x-based machine, check out AppleTalk over IP.
For developer information on AFP, see the now somewhat dated Apple Filing Protocol Programming Guide. There's also a technote TN3151: Choosing the right networking API.
AFP has served Apple well. It was simple and easy to use - and it was reliable. But since we live in a TCP/IP and Windows-based world now, it has outlived its usefulness.
It's well past time to retire it.
Read on AppleInsider

Comments
The former: APFS: Apple File System is how Apple wants you to format disks. This is current.
AFP: Apple Filing Protocol - this is being cut out of macOS.
@Emoeller, AFP is only used for network storage (over Ethernet or Wi-Fi. This deprecation doesn’t have anything to do with a drive that connects to your computer using USB, FireWire, or the ancient SCSI protocol that went out of favor when the original iMac was released in 1998.
AFP - AppleTalk Filing Protocol was amazing. It allowed long file names (not 8.3 like DOS) and did indeed protect the integrity of files. At the time all Macs had networking in the form of LocalTalk 230 kbit/s... and AFP made it possible to copy files between computers. It was essential to the graphic industry and DtP as big files could be moved and file servers created. Ethernet boosted speed but AFP was slow until it moved from AppleTalk to IP. Apple really did some nice demos on file copying around the launch of AFP 2.2 with System 7.6. It was the USP for selling 7.6 to businesses as I remember it.
So many long forgotten names in here. Chooser! Wow!
I used to tinker with ResEdit and run through the tips and tricks in Ted Landau's magnificent 'Sad Macs, Bombs and Other Disasters books'.
I still have it and cherish it. It's untouchable. My wife always puts it on the throw out list but that book will probably be with me to the end.
As of 2022, Ted was still going strong but of course, retired.
As for HFS/HFS+, I really hope they keep support for it long into the future. I have a huge amount of my life stashed away on old disks and I'm sure some those files slipped the net as I migrated to other formats and the cloud.
https://kb.synology.com/en-me/DSM/tutorial/file_protocol_AFP_not_recommended
This sums up the general rule that I'm aware of: "There is no single better protocol, as NFS and SMB each have their own strengths and weaknesses. NFS is generally faster for transferring small to medium files, especially when encryption is used, and is better suited for Linux environments. SMB, especially modern versions like SMB3, performs better with large files and is more common in Windows-based environments."
What do you use?
Of course, stolen credentials are an issue, as there's not MFA by default. So adding a VPN with MFA would put that layer of protection in place. But 548 open isn't a particular danger.