In my limited understanding, one-way data binding could happen like the following:
On the back-end, I have a Node backend server. In that, I have a layer that communicates with the database (Model). I have a controller that exposes URIs that the frontend server can connect to (Controller).
On the front-end, I have a React frontend server (View). The frontend-server sends requests to the URI-s exposed by the backend server.
If the frontend server wants to get data from the backend, it sends GET requests to the URIs exposed by the server (Controller), the server fetches the data (Model), and sends it to the frontend server (View).
If the frontend server wants to post some data so it will be stored on the server, it sends some POST requests to the server, which in turn handles it and saves the corresponding data.
I read that one-way data binding is basically an observer relationship between the view and the model. The view registers a callback with the model, and when something changes on the backend, the model will call the callback, and it will update things in the view. But why is this necessary, if you can just send and receive data using the URIs exposed by the controller? Is this forced by React? Obviously I'm wrong about something, but for me it seems like its counter-productive because it creates tight coupling without using the Controller, that would behave as an interface between View and the Model.