Persistence

  • Thread starter Thread starter Ralph Lund
  • Start date Start date
R

Ralph Lund

Hi NG.

I am intersted in which persistence mechanism you are using in your
projects (which persitence layer - data access classes, or-mapping-tool)
(for databases)

Which experiences do you have?

Thx.
 
Ralph, I'm not really sure what you mean by this. Do you mean, where are
people persisting data? To a database, files, or something else?

In my experience this totally depends on the project and situation. I don't
really think there is a standard that will apply across all applications and
all situations.

Is there something in particular that you are considering?
 
I experimented with Bamboo.Prevalence for a while.
Bamboo is a persistence engine which keeps all objects in memory, as well
as serialize them to disk for restarts.
Quite fascinating, but I had some concerns with it:
Versioning: What happens to your existing datastore when you refactor classes etc.
Scalability: If your app is mostly reading, it is extremely fast for most applications, but writing requires a lock.
Hierarchy: Bamboo couldn't store objects within objects easily

So, back to Sql for me (at least for now).

http://sourceforge.net/projects/bbooprevalence
 
Back
Top