3 ms·
This is an example of an interesting problem with "innovative" databases which is vaguely like the OSI networking model The first layer is business need, witho
by VLM 13y ago
This is an example of an interesting problem with "innovative" databases which is vaguely like the OSI networking model
The first layer is business need, without one there is no point. You need to start here. Facebook is empty here, so no need for innovation and no concrete ideas about what to innovate about, means no point discussing arch or later tech.
The next layer is architecture. Do you need joins? Well then use them. Do you need transactions, or not? Basically a big key value store?
The final step / layer is tech. You can do a boring key value store on mysql just fine. There might be a slightly faster or cheaper software choice. Or maybe not. Or maybe some nosql thing fits the architecture.
This is a huge problem I see with "the whole market is going to be disrupted totally and only I know how" type articles. So I herd cats around a quasi-geographic database at work (not directly geographic, but related). The only way to change its scale or business needs is to modify the geography of the United States or dramatic demographic changes that would even theoretically take generations to breed the eventual customers. So layer one can't change for that job.
The arch doesn't seem like it can be improved very much. So layer two can't change for that job.
Therefore because layer one and layer two are static, layer three will utterly change completely. Because he says so. LOL