bgrommes That and a game engine for me lol. I genuinely just hate working with traditional databases and performance/size aren't a huge concern for my application. So I am writing a oobish db basically storing runtime classes as their full class structure instead of breaking them apart into tables but without any methods that a traditional oodb would also have for its objects. Everything is indexed so look ups aren't too bad performance wise, and most of the objects are write once and rarely update.
All of my custom classes are based on an abstract class of either ReferencedObject or LocalObject. Referenced objects are serialized and tracked with unique ids, local objects are serialized directly inside of other objects, if a referenced object has a property that is also a referenced object its id is stored instead of serializing that object directly into it, this allows me to maintain my runtime relationships. It will be a fun challenge to get everything working and making some design decisions that I can change later if I want to get more complex.
Right now just to get things up and running pages in the database store only a single object (and objects can span multiple pages / do not need to be stored in sequential pages), for now I am writing objects in their entirety, but once that is locked down I'll add setters for modifying individual object properties. It gets interesting working with properties that aren't a fixed size. I am also throwing in encryption just for fun, the current use case doesn't store sensitive data but may as well plan ahead!
The problem with doing this is trying to maintain scope! I don't need a feature rich database... I don't need a feature rich database... I don't need a feature rich database...