java web security [closed]

Question

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.

Closed 9 years ago.

Let me explain the problem. So, there is a data base which is pivotal for many app and I need to keep it safe. Also, I do not want to access that data base directly. I think of using materialized view. Is that a good solution? I need some suggestions about how to keep a master data base safe and synchronized.

,cheers.

Answer 1

What do you want to do exactly ? Do all the application need to write on the database ? If not for read only application you can use View in your database.

Otherwise the best way to keep your database safe it's to use constraint when creating your table.

Answer 2

I would use a different approach. Make a copy of your database and use your application against this copy during a QA / Pilot phase. Once you know your application is stable and doesn't introduce security or stability concerns, then you can start using your production database.

Adding a materialized view would probably be difficult to work with as you would need to inspect each updates before manually synchronizing with the master database. And since there will be significant delay between the updates and the synch you run into potential collision issues.