I may have gotten myself confused, when reading CRUD vs REST and how they are similar, so I wanted to explicitly ask: can I turn my CRUD application into a REST application, when I have a specific scenario, and will doing so be of any benefit?
My existing CRUD application uses data in a MySQL table that is mostly passive, but from time to time it needs to be updated. In my case the data represents various dimensions and specs of a motor that are changed or corrected from time to time. There is also a similar but "higher in concept" use case where instead of modifying the data in-place, it is versioned and historical records are kept. That is, say the current "row" of data is first inactivated, but is otherwise left in the database, and a new row of data is added with a new version number, which is then made active. That new data is then read for any future motor computations.
The CRUD has the following parts: * HTML form, submitting which transfers data to an "add/edit" script, which redirects to "view" script that shows the added/updated data.
I don't have a clue of how to convert this into a REST application or if I need to, or of doing so will make my life or someone's life better.
Can I have a more concrete example of what it will mean to convert my particular use case from CRUD, to REST? Will I need to change any URLs, interfaces, event handling, etc?