By backend/frontend let’s assume you are talking about a web app and the browser. If you can program, are comfortable with data structures, and gain familiarit

By backend/frontend let’s assume you are talking about a web app and the browser. If you can program, are comfortable with data structures, and gain familiarity with Nodes APIs, and finally can set up a database the only real distinction then becomes programming and data. But let’s examine why people fail at this so very badly. First, the compile target of the browser is the DOM. It’s an in-memory data structure. When you accept that reality and can actually write original code you no longer need large frameworks or vanity nonsense like jQuery. It’s just programming plus a standard data structure with a given API. If you cannot reach this pinnacle of clarity everything remains challenging and you will need other software to do it for you. Second, you need to understand transmission to talk outside the browser even on localhost. There are several options available. HTTP 1.1 remains the primary standard and WebSockets remain the only full duplex option, but WebSockets are inherently session oriented while HTTP remains session less. If this is not your language you are not ready to write any kind of backend for any web app in any language. That’s all there is to it, assuming you can program. I was writing JavaScript full time for 15 and almost never found developers who could do these things. It’s not challenging if you accept some minor level of self sufficiency.