database - Which design pattern to use for my usecase? -

my core usecase read/write database , directory server.

eg. createuser, modifyuser, associategroup, changepassword etc

i have several other functionalities done in several of these use cases. 1.) audit start of operation 2.) audit failure in case of exception/error 3.) validate data 4.) persist in db 5.) persist in directory server (ldap) 6.) notify in somecases password change 7.) audit success 8.) future else

i thinking of implementing in kind of decorator design pattern there better suggestions ???

thanks, vignesh

the data should have been validated long before persist it. move code service receives request.

"persist in db" , "persist in database server" same thing. you're overcomplicating it. comment suggests should prefer wording distinguish between relational database , directory, conclusion doesn't change.

notify password change separate use case.

the thing qualifies logging start, completion, , error. can around aspect if use language or framework supports aop, spring. it's middle tier feature.