Architecture advice for a form application

  softwareengineering

In my second year of CS, I’ve develop a web application using php that was basically a “form graph” with a crud backend.

I’ve never been satisfied with it, and I was right because it is poorly designed, and difficult to upgrade.

Now I plan to rebuild it using a different programmimg language (Rust using rocket.rs) for the sake of learning it.

However, as I will need to build an API using rocket.rs, I wonder if I can stay on an MVC architecture ?

The app is not really complex, there are several types of customers that realise differemt types of visit.

Do you have some advices or resources to help me follow good practices in this development ?

New contributor

trya2l is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

LEAVE A COMMENT