Comments on: Cal Henderson (Flickr) – Scalable Web Architectures: Common Patterns and Approaches http://www.krisjordan.com/2008/09/16/cal-henderson-scalable-web-architectures-common-patterns-and-approaches/ on Software, Frameworks, & Stuff Sat, 29 Aug 2009 05:39:48 -0500 http://wordpress.org/?v=2.8.4 hourly 1 By: Towards RESTful PHP - 5 Basic Tips - Basit - Live Your Life with Inspiration http://www.krisjordan.com/2008/09/16/cal-henderson-scalable-web-architectures-common-patterns-and-approaches/comment-page-1/#comment-8206 Towards RESTful PHP - 5 Basic Tips - Basit - Live Your Life with Inspiration Tue, 26 May 2009 18:48:46 +0000 http://www.krisjordan.com/?p=143#comment-8206 [...] A truly RESTful PHP application should be entirely stateless- all requests should contain enough information to be handled without additional server side state. In practice this means storing authentication information in a cookie with a timestamp and a checksum. Additional data can also be stored in a cookie. In the event you need more than a cookie’s worth of data fall back to storing it in a central database with the authentication still in the cookie. This is how Flickr approaches statelessness. [...] [...] A truly RESTful PHP application should be entirely stateless- all requests should contain enough information to be handled without additional server side state. In practice this means storing authentication information in a cookie with a timestamp and a checksum. Additional data can also be stored in a cookie. In the event you need more than a cookie’s worth of data fall back to storing it in a central database with the authentication still in the cookie. This is how Flickr approaches statelessness. [...]

]]> By: Marcyes / Cal Henderson (Flickr) - Scalable Web Architectures: Common Patterns and Approaches - notes by Kris Jordan http://www.krisjordan.com/2008/09/16/cal-henderson-scalable-web-architectures-common-patterns-and-approaches/comment-page-1/#comment-6934 Marcyes / Cal Henderson (Flickr) - Scalable Web Architectures: Common Patterns and Approaches - notes by Kris Jordan Fri, 08 May 2009 19:29:08 +0000 http://www.krisjordan.com/?p=143#comment-6934 [...] Cal Henderson (Flickr) - Scalable Web Architectures: Common Patterns and Approaches - notes by Kris... The whole article gets into a lot of details about how they scaled Flickr and well worth the read if you are into scaling web apps. Specifically I really like the db notes:Database is the hardest part to scale. If we can, best to avoid the issue altogether and just buy bigger hardware. Dual-quad opteron with 16GB RAM can get you a long way.What do you do when the hardware can’t keep up? We do a lot more reading than writing. Somewhere between 80/20 or 90/10 ratio of read/write. “Only a few people who like to caption pictures of kittens on the internet - but a whole lot of people who like to look at them.”Replication is the solution for the read write problem. Master-slave replication. Add more slaves, 1 master 3 slaves = 4 times the read power. Flickr is 6 reads for every write.  Problem is what happens when we need to push more writes? As we need more writes this doesn’t scale well - have to add a lot more boxes.MySQL query cache has bad performance in most cases. MySQL query cache: for any read query stores a pointer to the result if you perform the exact same query. Any write flushes it, though. So if you do 10 reads for every 1 write you’re unlikely to get a hit before cache is invalidated. If you only write once an hour or day then this is a really good thing. Otherwise turn it off. [via news.ycombinator.com ] [ business, entrepreneur, scaling, server, db ] 1978 Latest Updates from this link [...] [...] Cal Henderson (Flickr) – Scalable Web Architectures: Common Patterns and Approaches – notes by Kris… The whole article gets into a lot of details about how they scaled Flickr and well worth the read if you are into scaling web apps. Specifically I really like the db notes:Database is the hardest part to scale. If we can, best to avoid the issue altogether and just buy bigger hardware. Dual-quad opteron with 16GB RAM can get you a long way.What do you do when the hardware can’t keep up? We do a lot more reading than writing. Somewhere between 80/20 or 90/10 ratio of read/write. “Only a few people who like to caption pictures of kittens on the internet – but a whole lot of people who like to look at them.”Replication is the solution for the read write problem. Master-slave replication. Add more slaves, 1 master 3 slaves = 4 times the read power. Flickr is 6 reads for every write.  Problem is what happens when we need to push more writes? As we need more writes this doesn’t scale well – have to add a lot more boxes.MySQL query cache has bad performance in most cases. MySQL query cache: for any read query stores a pointer to the result if you perform the exact same query. Any write flushes it, though. So if you do 10 reads for every 1 write you’re unlikely to get a hit before cache is invalidated. If you only write once an hour or day then this is a really good thing. Otherwise turn it off. [via news.ycombinator.com ] [ business, entrepreneur, scaling, server, db ] 1978 Latest Updates from this link [...]

]]> By: High Scalability (1) | New York City Man - Alessandro Pistilli http://www.krisjordan.com/2008/09/16/cal-henderson-scalable-web-architectures-common-patterns-and-approaches/comment-page-1/#comment-2183 High Scalability (1) | New York City Man - Alessandro Pistilli Sat, 21 Feb 2009 19:37:58 +0000 http://www.krisjordan.com/?p=143#comment-2183 [...] Cal Henderson (Flickr) - Scalable Web Architectures: Common Patterns and Approaches:http://www.krisjordan.com/2008/09/16/cal-henderson-scalable-web-architectures-common-patterns-and-ap...  [...] [...] Cal Henderson (Flickr) – Scalable Web Architectures: Common Patterns and Approaches:http://www.krisjordan.com/2008/09/16/cal-henderson-scalable-web-architectures-common-patterns-and-ap…  [...]

]]> By: links for 2008-12-02 http://www.krisjordan.com/2008/09/16/cal-henderson-scalable-web-architectures-common-patterns-and-approaches/comment-page-1/#comment-861 links for 2008-12-02 Tue, 02 Dec 2008 21:02:16 +0000 http://www.krisjordan.com/?p=143#comment-861 [...] Cal Henderson (Flickr) - Scalable Web Architectures: Common Patterns and Approaches | Kris Jordan (tags: scaling scalability php flickr architecture) [...] [...] Cal Henderson (Flickr) – Scalable Web Architectures: Common Patterns and Approaches | Kris Jordan (tags: scaling scalability php flickr architecture) [...]

]]> By: Towards RESTful PHP - 5 Basic Tips | Kris Jordan http://www.krisjordan.com/2008/09/16/cal-henderson-scalable-web-architectures-common-patterns-and-approaches/comment-page-1/#comment-855 Towards RESTful PHP - 5 Basic Tips | Kris Jordan Tue, 02 Dec 2008 06:37:54 +0000 http://www.krisjordan.com/?p=143#comment-855 [...] A truly RESTful PHP application should be entirely stateless- all requests should contain enough information to be handled without additional server side state. In practice this means storing authentication information in a cookie with a timestamp and a checksum. Additional data can also be stored in a cookie. In the event you need more than a cookie’s worth of data fall back to storing it in a central database with the authentication still in the cookie. This is how Flickr approaches statelessness. [...] [...] A truly RESTful PHP application should be entirely stateless- all requests should contain enough information to be handled without additional server side state. In practice this means storing authentication information in a cookie with a timestamp and a checksum. Additional data can also be stored in a cookie. In the event you need more than a cookie’s worth of data fall back to storing it in a central database with the authentication still in the cookie. This is how Flickr approaches statelessness. [...]

]]> By: Kris http://www.krisjordan.com/2008/09/16/cal-henderson-scalable-web-architectures-common-patterns-and-approaches/comment-page-1/#comment-154 Kris Thu, 25 Sep 2008 18:40:27 +0000 http://www.krisjordan.com/?p=143#comment-154 130K is what I meant to record, thanks for the catch! 130K is what I meant to record, thanks for the catch!

]]> By: Chris http://www.krisjordan.com/2008/09/16/cal-henderson-scalable-web-architectures-common-patterns-and-approaches/comment-page-1/#comment-138 Chris Mon, 22 Sep 2008 17:46:35 +0000 http://www.krisjordan.com/?p=143#comment-138 In the top of the article, did you mean 130K? or 13K? Thank you for posting all the write ups from the expo, it will save me a lot of work as I explain the sessions to my co workers. In the top of the article, did you mean 130K? or 13K?

Thank you for posting all the write ups from the expo, it will save me a lot of work as I explain the sessions to my co workers.

]]>