Web applications are evolving and some of the web development concepts are also evolving and mostly based on the need of today's world. It is important that every developer should understand the modern best practices and work based on them. If we are building a web application, validation is very important. In most cases, the validations are done only on the client side and server-side validation is ignored unless the data received from the front end is very sensitive. If we are building an application for customers who store sensitive data on a database, it is very important to make sure we accept clean data from the front end.
One of the biggest reasons why we do server-side validation is that people manipulate the backend calls and try to bypass the validation done on the front end and directly provide data to the backend. Even if we have enough validation in place, it is easy to manipulate the calls sent to the backend and provide updated values. It is the responsibility of every user to keep their credentials on their browser safe but if there are fundamental problems in the application on validations, it can be hard to control exploits.
Sometimes it can be painful to do validations for each and every field on the server side. People mostly check if the data is received in the right format and some basic things are sorted but it is important to validate everything in the backend as well and provide feedback to the users then and there and even to the level of each field. This can prevent issues related to data injection and data manipulation. It will also be easier for the developer to avoid issues that would occur because of this in the future.
The next obvious question a developer would usually get is if doing validations directly on the backend is good or if we should have the validation replicated in the front end. This means it is good to call the backend and ask for each and every action or it is okay to replicate all the validations on the front end. I would say for smaller applications with a high-security need, a call to the backend for each and every validation is not a big deal. But for enterprise applications where there are too many fields and too many dependencies on the backend, it can be hard to make calls for each and everything to the backend. A heavy-weight application can have the validation logic implemented two times where one would be on the front end and another would be on the back end. I understand it can be an overhead sometimes but it can save a lot of time for us if the app is supposed to grow in the future.
Client-side validation is also something that developers should not ignore just because we implement logic in the backend. Client-side validation gives a good user experience and should not be skipped on forms that are big or any form for that matter.
If you like what I'm doing on Hive, you can vote me as a witness with the links below.
 |
 |
 |
 |
 |
 |
