New answers tagged

0

The usual procedure for syncing rows in a database would be to initiate a transaction session. Before updating your row you read a second instance of the same row from the database (during the transaction session to avoid changes in the meantime) and compare any column's data for changes. As comparing any column can be a performance intensive task especially ...


0

The data mapper has to know about the unit of work. You would typically pass the UoW to the mapper using DI. I understood why they are both important and when to use them but, I couldn't find anywhere how the Data Mapper can "know" that a save method, for example, was called in the middle of a transaction or not. A single UoW instance represents one ...


0

The boundary for a Unit of Work is time. It answers the question: What all are we changing in this one transaction? The boundary for a Data Mapper is space. It answers the question: What all is part of this one data structure? The unit of work is used to prevent hitting the database to often by sending every little chunk of info one at a time. The data ...


10

We've had a few problems where a contractor changed something in a common project and unknowingly this breaks a number of other solutions That's is unfortunate We're currently trying to decide a new software architecture in our company STOP. You have a process problem, not an architecture problem. A much simpler, and more valuable, fix to this ...


1

To put all the applications in one solution is to say that all of the applications are related somehow. If they aren't, don't put them in the same solution. What you really are after is code-reuse. Since you don't specify a technology stack I'll list out some options in multiple technologies. These allow you to share code without stuffing applications ...



Top 50 recent answers are included