The first version of the Network File System, or NFS for short, was published by Sun Microsystems in 1985. The name is a bit misleading because today NFS is not the actual file system but the protocol used between the clients and the servers with the data.
The NFS protocol was designed to allow several client machines to transparently access a file system on a single server. One of the design goals was to allow a broad range of operating systems and processor architectures to implement NFS. Most operating systems have extensive native support for NFS, including Linux and macOS, but also more "exotic" systems such as FreeBSD or Solaris. Newer versions of Windows however, have native support for mounting NFS.
Today there are only two versions of the NFS protocol left in use: Version 3, which was published in 1995 and version 4 in 2000. NFS 3 is still by far the most common version of the protocol, and is the only one supported by Windows clients.
There really aren’t many. Being such a dated filing system, NFS hasn’t been able to adapt to the ever-changing needs of storage users today. It's like the lowest common denominator of storage because almost all operating systems can access NFS version 3 storage.
Most of the disadvantages of NFS stem from the fact that it was designed decades ago and for the communication with a single server. So what else makes NFS faulty?
Although Quobyte supports both version 3 and 4 of NFS, it also comes with native drivers that have built-on failover, load balancing, parallel IO and end-to-end checksums. Because of these features, there are no performance bottlenecks when you use Quobyte, unlike NFS, thus making it a more suitable option for most storage needs.