Split database
Posted by: Tom Taylor
Date: December 03, 2017 02:04PM

I have a question regarding database design in more secure web applications. With more secure I don't mean banking websites, but some kind of business websites with public areas including frontend with free user registration with profile management, but also backend for companines with login for employees and appointment management and other tasks. As far as I understand, a common pattern seems to be separating frontend/backend and accessing database through an intermediate layer, which is communicating to the database as well as to frontend/backend.
But are there also patterns dealing with splitting the database also? I don't mean sharding, but rather putting sensible company information and logins into one database and user profiles and their logins into another. Or is the intermediate layer ensuring enough safety and therefore the only common pattern to separate database access?
I did a research but only found topics about access regarding database frontend/backend, which is not compareable to modern webservers.
Kind regards...Tom

Options: ReplyQuote

Written By
Split database
December 03, 2017 02:04PM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.