Many web applications developers often make that mistake of creating their codes on the application-side that make their applications execute more functionalities before they travel to the database server then back to the web server.
A round trip transmission often becomes the glitch when the connection between the client and the server gets cut off for some reasons. This may even result to corrupted data that can compromise the proper functioning of the application and the database itself.
The data being transmitted may even get the attention of hackers for data capture which will lead to security breach.
Also, a .Net Developer must be aware that there a lot of “footprints” or integrated classes in the .Net Framework which makes it already heavy in the application-side processes.
Although there are many ways of protecting the data against SQL injections and session captures among others by using secure socket layers and command parameters or by simply using proper coding techniques still the burden of putting every processes to the web server will only make the web application slower and vulnerable to possible hacks.
One handy technique to ensure proper execution of any function that needs data processing is using Triggers inside the MSSQL database server. In this case, the data process becomes internal inside the database server unknown to the hacker and the data transmission becomes a one-way trip. Thus, it is obviously a more optimized way of programming than having to code every procedure in the application-side.
But be aware too that it is always a rule of thumb to balance the load of both the web server and database server.
Custom Christian Gifts
Customizable products: auto accessories, key chains, trailer hitch, license plates, frames, banners, bookmarks, coasters, household items, towels, coat rack, clock, magnets, ornaments, pens, picture frames, plaques, stickers, religious t-shirts!
Leave a reply