You map the Controller to an URL and fetch from that URL.
and some (sub)annotation of @RequestMapping(value="myUrl") define the method (put, get, whatever).
Alternatively, you can annotate with the dedicated subannotations: @PutRequest etc.
On the frontend you can use the fetch method.
That's all, basically.
The frontend will be a website with html, css, js as you mentioned created with or without frameworks like angular, vue, react, whatever you prefer.
You can run frontend/backend on different ports for development but if you want to publish your website it's probably best to work with subdomains for frontend and backend. You'll find configuration instructions on your webhoster / provider websites.
Sorry for the late reply, I'm just back from vacation ^^
From what I understand nginx correpsonds to the 'A' of the lamp environment, the web server. There are many other environments / predefined configs you can use to achieve the same, xampp is one I work with at home.
Many providers advertise supporting nginx or other server solutions, as mentioned before it's hard to recommend one particular solution for me at least.
Tashi N no worry, hope you had good holidays :)
I just see nginx popup everywhere in tutorials. I don't see why use nginx when a traditional LAMP is working as a charm. So for the moment I stay with the old school version :D
Here are a few threads that I found but lets include this from stackoverflow here
Tashi N Ilja Veselov Based on this topic, which I was looking for, I would like to know what is the purpose of nginx ?
Isn't the same to build a lamp environment to run a website ?
Or they are totally differents technologies ?