Re:Your own movie database in 5 minutes with IMDb API and Perl
by hvs on Monday November 21, 2011 @05:14PM
(#3263043)
Who would be paying for this DB to be hosted? It's always interesting to talk about making things "free", but in the end someone is paying for it.
[ Parent
| on HN ]
Re:Your own movie database in 5 minutes with IMDb API and Perl
by Jun8 on Monday November 21, 2011 @05:35PM
(#3263139)
Well, we're not talking of GB of data here, or are we? Let me, see: I think about 1K movies are produced every year, halve that and multiply by 100, you get about 50K movies total. Let's double that to account for shorts, independents, etc. and we get 100K movies in the db. How much info is for one movie? The crew of Titanic from IMDb as text is around 85K. Let's say less than 256K per movie. So we're looking at about 13GB of data. With lossless compression, e.g. LZW and some austerity, say ~5GB.
That's not tiny, but not huge. And the amount of download bandwidth will not be much, due to long-tail effects. A company like Google or Amazon, who stand to benefit a lot from such a db can easily accommodate this.
Re:Your own movie database in 5 minutes with IMDb API and Perl
by corin_ on Monday November 21, 2011 @06:20PM
(#3263278)
Amazon already have a database like that, called imdb. ;)
Re:Your own movie database in 5 minutes with IMDb API and Perl
by Jun8 on Monday November 21, 2011 @10:08PM
(#3263883)
Yeah, I meant one that wouldn't charge ~$15K for commercial access. One that would charge per db access would be nice.
But it's not exactly the money (after all fifteen grand, although excessive is not prohibitive) but the unreliability factor: if you're building a business on a db API there should be a warranty that the company won't decide to abandon it or cut your access unreasonably.