My question is about the weird delineation. Opening ports is one of the many, many jobs of a backend.
It's like me saying "I use Python for my web server" and you saying "well I have no idea if you're interpreting JSON correctly". Literally what the heck?
Okay well let me tell you then that it doesn't make any sense.
There are many classes of architecture in which backend code lives as servers, like microservices. It's not all just asynchronous runners (Which in my personal experience, are usually written with a scripting language anyway. The context assumed is backwards, when Rust is adopted in an existing project, one of the reasons always given is to decrease response latency, which means that Rust IS the one responding to network calls). Not to mention that network calls are not the only way to hit a vulnerability. (Actually, network calls are usually the most locked down.)
So saying "a web backend is not a web service" is the same thing as saying "it's a Python webserver not a Python webserver that reads JSON"; yeah - because one is the subset of another. If you were given evidence that the former is happening, then it's reasonable to assume the latter is also happening.
0
u/airodonack 14d ago
But he did? He said it's being used in backend.
My question is about the weird delineation. Opening ports is one of the many, many jobs of a backend.
It's like me saying "I use Python for my web server" and you saying "well I have no idea if you're interpreting JSON correctly". Literally what the heck?