VistaDB 3 Architecture

written by Jason Short on Tuesday, May 22 2007

I get emails and PM’s quite a bit asking me about our architecture and if we are going to redesign for speed / memory / whatever. Let me just publicly make a few statements about the VistaDB 3 engine.
The architecture is amazingly clean. It is very well designed and built for the future. Adding in LINQ is not a rewrite, or even a redesign. It is another engine to call our core routines. Mike and Alexey did a great job with the VDB3 engine. 
The VistaDB architecture has been reviewed by Microsoft and several MVP’s as well. Ralf’s Sudelbücher Blog entry about Dot Net design, and he uses VistaDB as an example case study as well.
As many long time coders will recognize the pattern of software:
  • Version 1 - messy code, but scratches and itch for someone and a lot is learned in the process.
  • Version 2 - Usually a total redesign from the lessons learned in the first effort.
  • Version 3 – Usually suffers from code bloat as a number of third parties come in and add everything but the kitchen sink. Normally suffers from trying to be all things to all people.
Here is a brief history of the code…
Apollo was built by others. The VDB team modified it and tweaked it, and built some stuff on top of it. After studying it, they learned a lot and built VDB2.
VistaDB2 was their actual first built engine from scratch. The SQL parser was not from scratch, but the engine was. And as most of us long time coders know, you build the first one to throw away. You learn your lessons and Version 2 is usually the best version. VistaDB3 is that second built engine from scratch. The parser is from scratch this time too.
So in some ways this is a generation 3 product (marketing mostly), but in the technical aspects this is really a generation 2 product. Where we are still lacking is in the documentation department. That is really at the generation 1 stage. It was never really a priority before and was not treated as a project within the company. It is now, and I know we have a ways to go still. It will get better, I promise.

Similar Posts

  1. devLINK 2007 – post show analysis
  2. Looking ahead to 2008, and back at 2007
  3. Set any 2008 Resolutions or goals?

Comments are closed

Options:

Size

Colors