Object Oriented Databases with db4o - One of the most notable initiatives in the business software development industry in the last few years is the simplification of data access. The core complication lies in the impedance mismatch between relational storage and object oriented code higher in the stack. Far too much plumbing is required to map object properties to columns in result sets, deal with data type variations and handle other annoyances. The most popular response to the problem has been to leave relational storage in place and introduce ORM (Object Relational Mapping) frameworks to automate the conversion between relational and object oriented structures. This approach is popular in business environments because having a relational database under the hood offers many advantages such as ease of reporting and integration. Object oriented databases, however, offer an interesting alternative....
Linq to Object Performance - Linq (specifically Linq to object) really has improved the "feel" and readability of .Net code by turning what we used to do with flow control, like loops and conditionals, into a query expression. Few people love tight code during development more than I, but I also have to support applications as they age. As the user base and application data grows performance almost always becomes a concern. In that vein I figured I'd whip up a simple test over a sizable amount of data and compare the execution times of a Linq and a traditional approach to filtering a list. First I needed something to build a list of: public class Movie { public string Title { get; set; } public TimeSpan RunTime { get; set; } } Then I filled...
