I just came across
Elliott O'Hara's
blog post about db4o. If you're a C# developer an you wrote at least one application where you use a repository pattern for making your domain objects persistent this might interest you. Elliot uses a Generic Repository interface and then provides a subclass Db4oRepository. Nice blog to remind us about db4o's simplcity! (source code included)
-
Posted by Anonymous on 3/20/2010 6:42 PM
You've been kicked (a good thing) - Trackback from DotNetKicks.com
-
Posted by elliott.ohara on 3/20/2010 6:42 PM
Hey guys, I'm Elliott.
Just joined the forum. Any questions, yeah, ask away.
Is anyone interested in a hosted server or does everyone pretty much use embedded?
I was thinking about creating a hosted server to try and spread the gospel. Just wondering if there's a demand.
Oh, yeah, all the source isn't there in downloadable form, but I'll get it posted tonight.
-
Posted by German Viscuso on 3/20/2010 6:42 PM
Hey Elliott!
Thanks for the blog post man, it was cool! I believe there might be some interest in the community to do hosted db4o but there are limitations in the C/S version of db4o such as speed (compared to embedded mode it's slow) and scalability (you're not going to be able to work with tons of clients transparently).
Also, did you know that you can expose db4o as an ADO.NET DataService?
http://developer.db4o.com/ProjectSpaces/view.aspx/AstoriaDemo
Best!! (keep db4oing =)
-
Posted by elliott.ohara on 3/20/2010 6:42 PM
Thanks!
I really don't wanna expose it as a ADO.NET DataService.
IMO that's moving backward. The whole beauty of ODBMS is the ability to work without making something into something it's not (a row in a table).
Thanks for posting my blog though. Thinking about my next one now!
-
Posted by German Viscuso on 3/20/2010 6:42 PM
Well said, you have a point there.
We're all waiting for your next blog post ;-)
Best!!
Loading, please waiting...