"What is claimed is: 1. A method for lofting and cutting a flat starting blank in a plane and for transforming the starting blank by compounding into a plate to be applicable to a specified patch on a surface having non-zero Gaussian curvature, said surface representing a 3-D shell structure to be fabricated by assembling plates comprising:"

via http://en.wikipedia.org/wiki/Document-oriented_database "But if anything I wrote sounds vaguely familiar because you somehow managed to dumb your RDBMS into storing structured data in BLOBs, added versions and timestamps on all records, grappled with minimizing transactions and locks, denormalized data like there’s no tomorrow, or relied too much on a message queue, then time to rethink. Are you using a hammer to polish your china? (Tip: not a good idea, invest in soft cloth) The thing about relational databases, dumbing them down doesn’t create a dumb database that you can scale easily, and doing read consistency on top of write consistency is two problems to solve. It’s still a shared resource programmed in COBOL pretending to be a mainframe from the day structured data would fit nicely in tabular form. Which, granted is perfectly fine for a lot of applications. And insufficient for others."