I am confused (easily done). To me model is the data from the database sent back as JSON.
When I think of that in an Angular context, when two-way binding is configured, it makes me think the framework is watching/polling the database so that when some other user/process/etc. updates the database, the other user(s) will see the changes in x number of milliseconds. Is that right?
One way binding makes me think it is just like a regular webpage now. I fetch a page and it is updated like it always has been. I have to press a button or some other event to get it to go back to the server and update the webpage, just like I always have with regular old JavaScript and no library (though I use jQuery a lot).
Do I misunderstand these? Why would I bother with one-way binding, if I am correct? I could always do that, so is one-way binding meant to be used with a database that is updated often? Facebook uses it so it seems I am way off.
(I understand how view and model are connected to each other in Angular. I don't know if the application that uses the database with a lot of CRUD will dictate I need two-way. Timing issues, etc. aside.)