May 4th, 2010, 03:31 PM
Single DB - Multiple Web App Shared Data locking design?
Can anyone suggest a design approach for managing the state of a object as it is shared between two different web applications that are deployed on separate application servers but using the same database?
- AppA creates a request object
- AppB approves the request object
- AppA can not modify the request object if AppB is reading the object
Use a "state" attribute in the object that is persisted to the DB which will be checked by both apps when reading and writing the object. Depending on the state you can read and then modify the request object.
Can anyone suggest an alternate approach? Something clever maybe with Spring/Hibernate ?
Tags for this Thread