This link has been bookmarked by 24 people . It was first bookmarked on 14 Apr 2007, by Joel Liu.
-
09 Jan 08
-
26 Apr 07
-
25 Apr 07
-
Frameworks don't solve scalability problems, design solves scalability problems. I picked up a word from Joe a few years back and find myself using it a lot: "friction." When referring to framework and tooling, "friction" is a (subjective) measure of how much the tooling gets in your way when trying to solve a specific-case problem. I've come to evaluate frameworks based on two rough metrics: how far the framework goes in solving the general case problem out of the box and how little friction the framework creates when you have to solve the specific-case problem yourself. When a framework finds a balance between these two areas, we call it "well designed."
-
-
22 Apr 07
-
19 Apr 07
Kenneth PriisholmWe've run against multiple (five now) separate PostgreSQL servers for a long time now. Not a replicating / mirror setup - separate databases with different data but with similar structure.
activerecord database performance rails scaling ruby valtechror unread
-
17 Apr 07
-
16 Apr 07
-
15 Apr 07
-
Dan CreswellThese patterns don't just apply to ruby/rails. Too many organizations still build on top of a single huge database.
-
14 Apr 07
-
13 Apr 07
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.