5 ms·
Scaling Disqus (YC S07)
- xtacy 16y agoFor such web services, what is the average/peak load on the network? Is it a bottleneck at all? Are the networks over provisioned?
- kingkilr 16y agoThe talk was recorded, and the video will be made available (once it's ready).
- orlandu63 16y agoCan we get a direct link to the PDF?
- ronnier 16y agoThis pulls out the notes: http://viewtext.org/?url=http://www.slideshare.net/zeeg/djangocon-2010-scaling-disqus http://viewtext.org/?url=http://www.slideshare.net/zeeg/djan...
- kfool 16y agoHow do you deal with schema changes? Do they force you to switch into a read-only mode?
- endlessvoid94 16y agoThis is invaluable, thanks for sharing. We're running into some really interesting problems building Djangy.com - this slideshow is a goldmine.
- siculars 16y agonice starcraft2 pitch at the end ;)
- technoweenie 16y agoI see someone playing Starcraft most of the time while I pass by their office (ours is right above theirs).
- patrickaljord 16y agoI thought they were using mongodb, any idea why they switched to pgsql?
- bdr 16y agoDisqus has used Postgres since the beginning. They also use mongodb.
- michaelfairley 16y agoThere was no mention of MongoDB in this presentation, but Disqus is listed on the MongoDB Production Deployments page: http://www.mongodb.org/display/DOCS/Production+Deployments http://www.mongodb.org/display/DOCS/Production+Deployments
- sr3d 16y agoHow many HAProxy server is being used? Just a main one with heartbeat for failover?
- deleted 16y ago[deleted]
- mdg 16y agoWhy is emailing an exception bad (Slide 48)? Can a small site get away with it ?
- simonw 16y agoIt's fine for small sites. You'll know when your site is too big for that feature from the pain in your inbox.
- tkaemming 16y agoA possible disaster scenario: connection issues with the SMTP server are causing the initial exception, resulting in webserver connections that are open for excessively long periods of time (unless you're sending the emails asynchronously), since the process is blocked first on the failed SMTP connection, then again on the exception email attempt (and you're still not getting any notification that something is broken, unless you're doing some other kind of monitoring!)