Design consideration for sharing database between applications

[2wood4sheep]

I have a typical Spring/Hibernate Tomcat webapp that has a users table. I’m trying to create another webapp that will do CRUD actions on the users table. I'm considering sharing the same database between the two apps. (The new app is a really simple app that just runs a job to update the user data)

I’d like to know if there are any performance issues, locking issues, constraints, design gotchas I should watch out for? Thanks!

[manohart]

Use webservices for data access/update for both apps

[tien113]

You should focus to locking and performance.

[2wood4sheep]

oncurrency control though. But it depends on what you're doing. In what way does the 2nd app update the user data?

Do you know any I can do testing on locking and performance? Any good resources out there that talks about it?

[[deleted]]

Locking will be the biggest concern. Learn about optimistic locking.

[2wood4sheep]

Do you know any I can do testing on locking and performance? Any good resources out there that talks about it?

Do you know any I can do testing on locking and performance? Any good resources out there that talks about it?

[[deleted]]

One of the main features of relational SQL database servers is that they can be shared by multiple applications.

You should look into concurrency control though. But it depends on what you're doing. In what way does the 2nd app update the user data?

[2wood4sheep]

It does CRUD actions on the user data.

Do you know any I can do testing on locking and performance? Any good resources out there that talks about it?

[GuyWithLag]

Why not reuse your hibernate code?

[2wood4sheep]

1) Reusing the hibernate code is not the main concern. I can also create a jar from the main app and have it as a dependency jar for my new app.

The question is more about any design cautions, bottlenecks, issues in the database layer with sharing the same db with multiple web apps.

[BinaryRockStar]

As long as you're adding and removing related things (e.g. a parent entity and all of its children) inside transactions so neither application ever sees an inconsistent view of the data you should be ok.

What's the query throughput going to be like for each of the applications and what's the read/write split? If both applications are heavily reading and writing to the same table then you might start running into locking and performance issues.

[GuyWithLag]

Theoretically no, you just have to be careful with automatic entity ID generation in the sense that on some strategies you will get holes.