20 June 2003

ODBMS for .NET

So, I've have an itching lately to write a .NET-based photo gallery that's as robust as my old photo gallery software, Gallery (http://gallery.sourceforge.net).

In doing so, I'm trying to keep alot of the same requirements - namely, the lack of access to a database. Gallery is all file based and doesn't require that you have database access at your hosting facility. I think this is very important, myself, as I don't want to pay for the upper level hosting options that include SQL Server. Access is always an option, sure, but am shying away from this option due to this article:


http://aspalliance.com/PeterJohnson/JetAdvice.aspx

So, that left with me with one option: an in-memory object database. Talking with Scott Watermasysk, he pointed me to a .NET port of Prevayler: Bamboo (http://bbooprevalence.sourceforge.net), but Prevayler requires a totally different mindset, so I kept searching. One of my co-workers joined me in my search and came across Matisse (http://www.matisse.com), which looks like exactly what I'm looking for. Unfortunately, it's a commercial product and I'm only wanting it for my personal projects. :)

So, spreading the love and research that I've found so far, but calling out for any references that you guys may know of a free (or cheaper) equivalent to Matisse?

Filed under:

Comments

# Jim Arnold said:


Can you explain what it was about Bamboo that made you keep searching?

Jim

Friday, June 20, 2003 2:18 PM
# Jason Alexander said:

Ideally, I want to write the Photo Gallery code so that it will ultimately be open source.

The problem with prevayler concepts are that they're very foreign to most people. Especially less-advanced developers that are likely to download my code and want to use it for their own personal site. Granted, they'll have some type of geek background, I would assume the majority of my intended audience would not have a background in software development.

Prevayler has a very high learning curve. Event with the transparent prevalence, it's still an odd concept to wrap your head around.

Because of such, I need an alternate product that stays true to the concept of a database. Not a prevalence layer/engine.

As much as the geek in me would love to use it in my application, it just doesn't seem practical for my use.

Friday, June 20, 2003 2:26 PM
# Ken said:

.NET really needs a good photo gallery app. I've been thinking of writing my own, but not for a while. I'd want a DB backend, but it would also be nice if one came out with a XML backend... wouldn't be too bad.

Saturday, June 21, 2003 7:33 AM
# Harry said:

Have you checked out PERST for C#? http://www.garret.ru/~knizhnik/csharp.html

Sunday, June 22, 2003 9:50 PM
# DarthAPO said:

Perst is kinda cool.

If you wanted something more of a database, you could use Sqlite: http://www.sqlite.org/

I've used it with Python rather often. I dig it. ;-)

I saw that they have some .NET bindings (which I've not used, so I can't vouch for): http://www.ag-software.com/SQLite/default.asp - another one - http://www.redloop.com/larsde/software/sqlitenet.php

And, interestingly enough, those wacky Mono folks are building a sqlite DataProvider: http://www.go-mono.com/sqlite.html

There's probably more just a google away.

Wednesday, June 25, 2003 9:15 PM
# Max said:

why bother with a "real" ODBMS for Gallery over just plain serialization? Gallery, as far as I could tell, pretty much uses rudimentary serialization in the first place...

Friday, January 23, 2004 7:29 PM
# AK said:

How about "db4o"?

http://db4o.com

Friday, November 16, 2007 2:57 AM

Leave a Comment

(required) 
(required) 
(optional)
(required)