Software Architecture: Unit of Work design pattern discussion
Posted
by santiagobasulto
on Stack Overflow
See other posts from Stack Overflow
or by santiagobasulto
Published on 2010-06-05T21:14:34Z
Indexed on
2010/06/05
21:22 UTC
Read the original article
Hit count: 299
Hey everybody.
According Martin Fowler's Unit of Work description:
"Maintains a list of objects that are affected by a business transaction and coordinates the writing out of changes and resolution of concurrency problems."
Avoiding
very small calls to the database, which ends up being very slow
I'm wondering. If we just delimit it to database transaction management, won't prepare statements help with this?
© Stack Overflow or respective owner