Magic Scaling Sprinkles

[...] at all. So we set about to re-write Querulous using my favorite modularity techniques: Dependency Injection, Factories, and Decorators. In other words, everything you hate about Java. The design [...]

[...] into a blog-post illustrates how I often use the Decorator pattern with Factories and Dependency Injection to structure programs. This is closure writ-large, and is a different way to think about [...]

[...] one thing on top of another like so many legos. Let’s look at an example. Here I have a Query object, with methods like #execute(). I want to add timeouts around all queries. I start by creating [...]

[...] is that each “query” (e.g., Users.order(...)) returns not an array of data, but a query object that one can manipulate still further. Only when you try to iterate through the data is a SQL [...]

[...] could be configured by any programmer anywhere, regardless of whether they have access to the source code that actually instantiates and executes queries. Any user of Querulous can decide if she want [...]

[...] therein lies the rub. All of my open-sourced projects share two attributes. First, the source code is extremely stylized and meant to be /read/ more than /used/. They are literary [...]

[...] that this would not be possible if not for a defect in our programming in the face of the massive scale of the world. Everything has become a giant fucking heap. The modern world is profoundly [...]

[...] but its nicety is just an illusion. All that boilerplate is really important when you work at massive scale and where efficiency really matters. These magic numbers like the thread pool size and the [...]

[...] and ActiveRecord. So I began work on Arel, an Object-Oriented interpretation of the Relational Algebra. The Relational Algebra is a mathematical model for representing “queries” on [...]

[...] , but it wraps that execution in a Timeout. As an aside, it is interesting to note that the Decorator pattern is just the Object-Oriented equivalent of function composition in a functional language. [...]

[...] . This gist which I will someday re-write into a blog-post illustrates how I often use the Decorator pattern with Factories and Dependency Injection to structure programs. This is closure writ-large, [...]

[...] not the exception?”. I saw, unfortunately, that in order to do this I would need to re-write ActiveRecord. So I set out to re-write ActiveRecord. I announced my intentions (and then began a [...]

[...] Pre-requisite: please read my article on Write-through caching to understand why this is useful. Most caching solutions in the Rails world involve [...]

[...] -day occurrence and you must plan accordingly. Fortunately there is a solution, and it is write-through caching. At the same time as writing to the master database, write “through” a cache [...]

[...] -oriented code is how easy it is to write isolated unit tests of that code. To test the timeout functionality of the TimingOutQuery we don’t need to interact with a database at all. We can write [...]