4 ms·
A Visa application system doesn't strike me as an obvious candidate for a relational database. I would rather store all the information related to a visa applic
by cm2187 11y ago
A Visa application system doesn't strike me as an obvious candidate for a relational database. I would rather store all the information related to a visa application in a document store with a relational database only used as a sort of index. I wonder if lots of systems are not built using relational just out of habit. And then bump into these problems.
- andreasklinger 11y agoI assume the technical fundaments are older than document databases were popular in enterprise and reliable on scale
- icebraining 11y agoSay you're the tech lead for the project, built before 2001 [1], and you need to hire a vendor that can provide a cluster that won't break with 100TB+ and guarantee long term support, possibly for decades. Who would you call? [1] http://www.law.umaryland.edu/marshall/crsreports/crsdocuments/RL31512_02112004.pdf http://www.law.umaryland.edu/marshall/crsreports/crsdocument...
- bigiain 11y agoI don't remember the exact timeframes, but I suspect Digital and Sun Microsystems were likely looking choices around that time. (Sun was the default choice for Telco billing systems around then...)
- needusername 11y agoWhy do you need a cluster?
- jpatokal 11y agoBack in 2001, 100TB was massive. The first 1 TB HDD didn't roll out until 2007.
- needusername 11y agoIt's my understanding that most of this is pictures and not "actual rows", the database without the pictures should be much smaller. You could put the pictures on a SAN.
- eru 11y agoWhy not? There should only be at most a few billion rows (since you can't have more visa applications than humans).
- 4ad 11y agoOf course you can, you might need to apply for a visa multiple times if you want to visit multiple times. In fact, most tourists have to do that. It's still about the same order of magnitude though.
- eru 11y agoYes, that's what I meant.
- bigiain 11y agoNever bumped into the "beautiful flexibility" of ERD databases - where the app devs assume all responsibility over things that database designers _really_ should be saying "Hell no!" to? +------------+------------+--------------------------------+ | asset_id | asset_name | asset_data | +------------+------------+--------------------------------+ | 2147483646 | firstName | Joseph | | 2147483647 | lastName | Bloggs | |-2147483647 | phoneNumber| +1 415 555 1234 | |-2147483646 | email | joebloggs@gmal.com | +------------+------------+--------------------------------+ (I think I still have brain damage from trying to get "too smart" with a Magento eCommerce site once...)
- duaneb 11y agoThe flexibility typically comes from transactions and joins, something document store proponents typically shy away from. And yes, if you give stupid devs powerful tools they will shoot themselves.
- eru 11y agoIt's not only flexibility, but also discipline and taking away choices (for bad modelling) that comes from following the relational normal forms.
- mseebach 11y agoTo a conservative government purchaser working with a conservative software vendor on a system that doesn't do anything remotely fancy or magic, a relational database (Oracle, specifically) was most certainly the right choice 10 years ago, only moderately less so today. And just to be clear, that's (mostly) a good thing.
- duaneb 11y ago> I would rather store all the information related to a visa application in a document store with a relational database only used as a sort of index. Now you have two problems.