Re: Heavy DB writes design solution? (celko & aaron)

[Aaron Bertrand [SQL Server MVP]]

In a very simplistic model, or one where all of the business logic can be
repeated in both the middle and data tiers, sure, I guess...

On 5/29/09 7:30 AM, in article
57f43805-b65a-4191...@o14g2000vbo.googlegroups.com,
"sql...@live.com" <sql...@live.com> wrote:

> For an application that experiences heavy writes to the database,
> could this be a solution?
>
> The application itself uses a 3-tier model. When a entity needs to
> persist, the DAL creates the query needed to persist (could be an
> update/insert) and then queues it in a sequential multi-threaded "DB
> writer" tool. Then the DAL inserts the entity into a cache.
>
> On a incoming read request, the DAL requests the recordset from the
> database, transforms it into a collection of entities. It then checks
> the entities to see if there is an "updated" version in the cache. If
> so, replace that specific entity with the one in the cache. For search
> based queries, the DAL will query the cache in addition to the
> database and then merge both sets. This will solve the stale data
> reads.
>
> Would this be a solution?

[sloan]

Here are some great posts (2 URL's below) with great advice:

It's a little confusing, because the OP of this post has the same return
address as the person who wrote the great advice below.
Maybe someone is using the same email address(??). I'm not sure.

http://groups.google.com/group/microsoft.public.dotnet.framework.adonet/msg/32e0df06375c47b6?hl=en
// sql...@live.com quote //
Linq, MVC framework, OR/M, entity model framework, datasets &
datatables are all pathetic hacks in .NET. Only idiots use this 1-2-3-
poof magic application techniques that are guaranteed to fail
longterm.
Get yourself a begineers level book on software engineering and design
patterns.
// end quote

http://groups.google.com/group/microsoft.public.dotnet.framework.adonet/msg/5184f02683f48f48?hl=en
// sql...@live.com quote //
Go get a beginners level book on concurrency, application
architecture, and database design.

// end quote

Here is another great post:
http://groups.google.com/group/microsoft.public.sqlserver.programming/msg/73bfbdeea81f6aad?hl=en
There is that advice again:
// sql...@live.com quote//
Get yourself a beginners level book on concurrency, application
architecture, and database design.
// end quote

I just added you to the blocked list on my laptop (forgot to do that
yesterday).
So this is my last-last good-bye.

I know, I know..........I'm one of the "only idiots" crowd.
http://groups.google.com/group/microsoft.public.sqlserver.programming/msg/353db1e958137f58?hl=en

<sql...@live.com> wrote in message
news:57f43805-b65a-4191...@o14g2000vbo.googlegroups.com...

[--CELKO--]

>> For an application that experiences heavy writes to the database, ..<<

Look at Kx Systems, Streambase and other streaming DBMS products.
They are designed to "drink from a fire hose" from the beginning. And
they allow you to query while millions of rows are being written.

One of the beauties of SQL is that there are sooo many possible
specialized implementations.