This post originated from an RSS feed registered with .NET Buzz
by Steve Hebert.
Original Post: design pattern search
Feed Title: Steve Hebert's Development Blog
Feed URL: /error.htm?aspxerrorpath=/blogs/steve.hebert/rss.aspx
Feed Description: .Steve's .Blog - Including .Net, SQL Server, .Math and everything in between
I've been looking for a design pattern, but I'm not seeing it yet.Â
Given an application where application state is fully contained in
memory, the database is merely a stateserver for restore purposes and
integration with the application is handled through staging
tables, I'm looking for a pattern that discusses a LazyWrite that
incorporates a Unit of Work pattern where transactions cancel the
staging record and update the state database simulataneously.Â
Being a lazy write on the Unit of Work objects, it uses a background
thread to perform the actual write to allow the in-memory server to
continue responding to application-level interactions regardless of the
database load. The goal of the pattern is two-fold - keeping the
data in a known state where no transactions are lost in the event of a
power failure and performance of the in-memory server is not impacted
by database performance. If incoming transactions are not saved
in the time between processing and a power-outage, restarting the
server merely performs these transactions again once the in-memory
state is restored.
I have a feeling this may be a new pattern and there are several
combinations of patterns that work nicely in this type of application.
Perhaps I'll have to start writing about these and sharing.
Previous Topic
