<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: j2ee</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/j2ee.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2007-04-14T02:35:10+00:00</updated><author><name>Simon Willison</name></author><entry><title>Quoting Ryan Tomayko</title><link href="https://simonwillison.net/2007/Apr/14/j2ee/#atom-tag" rel="alternate"/><published>2007-04-14T02:35:10+00:00</published><updated>2007-04-14T02:35:10+00:00</updated><id>https://simonwillison.net/2007/Apr/14/j2ee/#atom-tag</id><summary type="html">
    &lt;blockquote cite="http://tomayko.com/weblog/2007/04/13/rails-multiple-connections"&gt;&lt;p&gt;The promise [of J2EE] was that of infinite scalability based on tooling, which assumes that designing scalable systems is a general case problem. I now firmly believe that this is flawed reasoning. Frameworks don't solve scalability problems, design solves scalability problems.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p class="cite"&gt;&amp;mdash; &lt;a href="http://tomayko.com/weblog/2007/04/13/rails-multiple-connections"&gt;Ryan Tomayko&lt;/a&gt;&lt;/p&gt;

    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/frameworks"&gt;frameworks&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/j2ee"&gt;j2ee&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/java"&gt;java&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ryan-tomayko"&gt;ryan-tomayko&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/scaling"&gt;scaling&lt;/a&gt;&lt;/p&gt;



</summary><category term="frameworks"/><category term="j2ee"/><category term="java"/><category term="ryan-tomayko"/><category term="scaling"/></entry></feed>