Search Results

If everything goes fine, do a single transaction at the end to copy the rows into the real table, then clear them out of the staging table. …

One of the benefits to transaction scope as opposed to a transaction is that you can use it without reference to the connection. … This allows you to potentially use it outside of the data layer so the business logic can decide whether two or more data operations should be part of the same transaction or not. …

Since you already have a Message Queue, put the message directly on that rather than the db and horizontally scale your Midpoint and App2 App1 -REST-> Midpoint Midpoint (load balanced, multiple ser …

The general solution to this is to have a clean up check which runs periodically. Service C: Perform Operation C Close A (via message to A?) Service D: Look for all open Operation A's …

With the trend for stateless calls no-one will expect a method call to require closing. But a "Connection" is expected to have state, open, close etc I would rename stuff to lean into that and instea …

No. Consider todays normal practice is to send the "IsAdmin" flag as a claim in a token. A token with an expiration of at least several minutes, if not hours. It's expected and accepted that there is …

The linked blog post is rather vague and seems be a confusion of active record and entity object pattens rather than using data transfer objects. Bear in mind that underneath whatever orm or wrappers …

You can't really handle the stock level reservation with a traditional database transaction. Because it's a human clicking through the order process, the transaction would simply be open too long. …

The traditional answer would be a "unit of work" pattern. But its not particularly good in my view. A better solution is to do away with the transactions. Or at least remove them from the business lan …