2 ms·
'... Six Apart didn't hire Brad -- they acquired LiveJournal from him and named him "Chief Architect" or something ...' Same result. '... their developer do
by bootload 20y ago
'... Six Apart didn't hire Brad -- they acquired LiveJournal from him and named him "Chief Architect" or something ...'
Same result.
'... their developer does not seem to be amazingly qualified to do what he's doing ...'
The thing that strikes me is the system is not layered enough. The API's the app developers should be calling would shield having to deal with these types of problems. nostrodemons [0] summared flickrs approach to optomisation. [1] So is it the lack of a scaling infrastructure where twitter is failing?
'... how many are dynamic and how many are cachable/static ...'
One thing I notice with twitter is the update on the sytem. Every 2 minutes.
For most users 5-10 minutes would probably be ample. I often wonder why they don't say "right you want RT, well here's the monthly subscription".
As for the dynamic and cacheable, the main hits appear to be reads of RSS public timeline. [2] RT creation allows no or little caching as the RSS would be built on the fly. Couple that with Rails in ability to talk to multiple db's [3] and you get bottle necks. Makes you wonder why they don't switch certain layers to perl?
'... definitely no Fitzpatrick ...'
Rare as hens teeth.
Reference
[0] nostrodemons, 'news.yc user'
http://news.ycombinator.com/user?id=nostrademons http://news.ycombinator.com/user?id=nostrademons
[1] nostrodemons, 'comments in Startup founders, what books did you find most helpful?'
http://news.ycombinator.com/comments?id=5715 http://news.ycombinator.com/comments?id=5715
[2] google groups, twitter development talk, Alex Pain 'we don't gaurentee
that you'll be able to collect contiguous sets of data from the
public timeline API method. It's our most-requested method, so right
now it's optimized for performance, not archival'
http://tinyurl.com/3xay7v http://tinyurl.com/3xay7v
[3] Twitter trouble, 'thereÂs no facility in Rails to talk to more than one database at a time', Ibid.