Experiences at Database Inventor

I am responsible for providing the overall vision, making sure that we test, test, test, for developing the abstraction models and for implementing them. Chief cook and bottle-washer as they say.

I have learned, or relearned perhaps, that even a technology that seems very complicated like a database engine can be slowly and systematically designed. One simple, well designed feature after another, until finally you have recreated a very complex thing from much simpler components. Tangentially, it is obvious from the way they operate that none of the large databases were ever designed carefully from the beginning. They would not be so difficult and cumbersome to add features to them now, nor would they have such poor performance....

All you need is to be innovative, inspired, optimistic and have a passion for database technology.

The primary difficulty has been conceptual. How do I overcome the difficulties of the Relational Database and make something superior in usability and performance. I believe I have solved that difficulty with my current design.
As far as performance goes, I have invented a database that can go through a table of 100,000,000 records and read 20,000,000 per second. It also supports a dictionary and a rich client which allows it to transfer data pointers that get dereferenced on the client side. This means that it can send less than 10% of the amount of information any other database would send in order to get the exact same results thus greatly improving network performance and reducing network overhead.
As far as flexibility goes, the database supports auto-joining tables, can traverse the hierarchy of relations and display all inherited columns as though they were present in the table in question, show all available metadata for the column/table/relation and can be extensively redesigned without rewriting dependant applications.
If you are interested in finding out more, helping me out with it or implementing it in your environment, send me a note....