Object Persistence Presenation in Charlotte, NC – Slides and Code

I had a blast presenting Object Persistence at the Enterprise Developers Guild tonight. I hope everyone (or at least some) enjoyed the sugar bus with the peanut M & M’s 🙂

As promised here are the slides and source code of the presentation. I was not able to touch on some areas as I did have a lot if information packed into a little over an hour. I’m glad though that some people got to start thinking “hmmm, I can do away with the SQL code?” 🙂

Let me know your feedback so that I can improve my presentations for next time.

You can download the slides and the source code here.

Object Persistence Presentation in Charlotte, NC

I will be presenting at the next Enterprise Developers Guild meeting in Charlotte, NC on April 24th, 2007 at 6:00 pm at the CPCC Central Campus. You can find more details here. I’ll be presenting about Object Persistence. I’ll be showing why you need to worry about Object Persistence and why this is an important part of any modern software architecture. I’ll be using the object database db4o in a demo that shows multiple, logical layers, several design patterns such as Model View Presenter, Facade, Singleton etc. Although simple, I’ll have a fully functional Windows application that can manage patients. I’ll be using Test Driven Development to hammer out the design using unit tests from scratch.

So, come join me and watch those objects having fun. Watch out for the sugar bus! Come to find out.

04-13-2007, UPDATE: I’ll make the slides and source code available shortly after the presentation.

db4o – Object Database for .Net

I have been using db4o (database for objects) for .Net for about a year and a half, and I have to tell you that you are doing yourself a disservice if you have not tried it, yet. It’s open source and it will save you tons of time. I will go into more detail in my upcoming book about Object Persistence including examples, but, db4o is one way to persist objects and that is by using an object database instead of a relational database.

If you have never used an object database before, think of it like this: you are already using .Net so you are already using objects. What you probably are not doing is using objects all the way to saving your “data”. At some point you have been messing with ugly SQL statements and maybe “mapping” objects or using a mapping layer. You may be using a “data layer” etc. All hog-wash!

db4o can save you about 50% of your development time. And that is a conservative estimate. I’ll be posting more including code in the upcoming months. Stay tuned.