The point is the problem of exposing a port, as opposed to the additional problem of whatever security concerns you imagine your backend "process" may have.
I suppose you may not imagine that exposing a port is somehow problematic. However, it is. First, an open port reveals many things[1] about your operation you would likely prefer not to reveal. Second, it requires Internet service that permits control over open ports, and the authority to utilize it, either or both of which may not be available to you.
I have no trouble appreciating the value of this, both for personal and commercial purposes. The inherent DDOS protection alone is a huge benefit.
[1] Off the top of my head:
a.) The ASN and, ultimately, the ISP you're using.
b.) The approximate physical location of your system.
c.) Through fingerprinting, your firewall device, and whatever problems it has.
Comments
The point is the problem of exposing a port, as opposed to the additional problem of whatever security concerns you imagine your backend "process" may have.
I suppose you may not imagine that exposing a port is somehow problematic. However, it is. First, an open port reveals many things[1] about your operation you would likely prefer not to reveal. Second, it requires Internet service that permits control over open ports, and the authority to utilize it, either or both of which may not be available to you.
I have no trouble appreciating the value of this, both for personal and commercial purposes. The inherent DDOS protection alone is a huge benefit.
[1] Off the top of my head: a.) The ASN and, ultimately, the ISP you're using. b.) The approximate physical location of your system. c.) Through fingerprinting, your firewall device, and whatever problems it has.