I am always a little suprized at how many companies decide that they need to develop a new database to solve the problems that they have. Instead of working on

I am always a little suprized at how many companies decide that they need to develop a new database to solve the problems that they have. Instead of working on making the problem solvable with an exsisting tool. Personally, I think it would be cool to write my own database as a side project. I would learn a lot. It is a cool thing to work on. It is also -hard-. Really -hard- to do it. There are millions of odd edge cases that preexisting mature solid database systems have implemented over time as they became aware of them. Usually, the shortcuts implemented in geen field new databases to make them fast or easy to use end up being impediments laster on down the line. All of that said in context of being a database being developed by a business to run their own business on. it is, or it will become a giant time consumer. Or you can redesign the code of the actual product to fit the quirks of the homegrown DB. At that point redesiging the code to fit an existing product will seem like a pretty good idea but now you have sunken cost syndrome. With all that said, I value diversity. Sometimes something brilliant can come out of doing things that are a bit crazy. I do wish that a lot more operting systems were created. It could be argued that when you might build a database to solve a product domain, a custom operating system would also get you part of the way. Most people when they hear "oh you should create your own operating system for that" will tell you, you are nuts. (for good reason). i think the same reaction some come with "You should create your own datasbaase system"