4 ms·
Expecting a good answer to this question in 30 minutes without any warning is totally unreasonable. Expecting anyone to implement a deployable, generalizable,
by mhewett 16y ago
Expecting a good answer to this question in 30 minutes without any warning is totally unreasonable. Expecting anyone to implement a deployable, generalizable, tested solution to this in two weeks is totally ridiculous. I wouldn't work at a place that asked questions like this or made development calendars with schedules like that.
- tlb 16y agoYet, companies who can pull off those feats are the ones who survive. A 1 TB database, even 5 years ago, shouldn't take more than a week or two to build properly. The solution I've used in the past, a Netapp file server with hashed directories of key-named files, takes zero programming and a couple hours to install. (You can easily read 5000 files / sec over NFS from one of their file servers.)
- parbo 16y agoI did this in three weeks: http://bitbucket.org/rogueops/vinzclortho/wiki/Home http://bitbucket.org/rogueops/vinzclortho/wiki/Home I worked on it on average two hours per day. It's not that ridiculous to believe that it would be (near) production quality in two weeks of fulltime work.
- mhewett 16y agoIt's not hard to get "near production quality". It is hard to get to production quality.