Jump to content
Larry Ullman's Book Forums

Separate Front-End By Back-End In An Application

Recommended Posts

Does it make any sense, security wise, to have the front-end separated by back-end of an application by storing the two sets of data in different databases? Or there are other ways how to separate one from the other, as per example by setting different privileges for users who access the database? Thank you.

Link to comment
Share on other sites

I'm not sure what you mean by "front-end" and "back-end" but having two sets of data is a very bad idea. While you might think you're adding security, you're also introducing redundancy, which leads to bugs in databases.


If by "front-end" and "back-end", you mean the public and administrative sides, then, yes, two different database users with different privileges is a very smart, secure approach. For example, the public database user may not be allowed to delete anything and may not have any access to specific tables, as appropriate.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Create New...