Mono, gcj, java, c++, what?

[dsr-mzpnVDyJpH4k7aNtvndDlA at public.gmane.org (Dan Ritter)]

On Sun, Aug 29, 2010 at 08:34:44AM -0400, Mark Woodward wrote:
> > You must be able to run this on many machines with a load balancer.
> >    
> These days? You'd be surprised at the capacity of $600 worth of computer 
> supplies. Its enough to run all but the very big sites.

I wouldn't be surprised at all. Now, after you've got it up and
running... what do you do for maintenance? Both software and
hardware. What do you do when you get slashdotted, or the moral
equivalent of same? What do you when the power supply fails? OK,
you spent the money for dual power supplies. What do you do when
the motherboard fails?

> Funny, but "stored procedures" are probably the best way to implement a 
> lot of functionality. They are "pre-compiled" by the databases, are 
> faster than raw queries, and can be modified without touching the web 
> code. My advice is to avoid databases that don't have such features. I 
> could start my "don't even think about using MySQL rant."

Some sites can't support the license fees for Oracle or DB2.
That leaves MySQL and Postgres, for SQL databases, and a whole
host of non-SQL systems of various sorts. No matter what you
start with, you may want to change it later on. Stored
procedures will make that a nasty pain.

Oh, and "modify the stored procedures without touching the web
code" is completely backwards. Your web code is going to be
changing all the time, because that's what people see and touch
and is where they make change requests. If you've got stored
procedures, you're going to have to change them to support the
new web code, all the time. If you must use them, minimize them.

-dsr-

-- 
http://tao.merseine.nu/~dsr/eula.html is hereby incorporated by reference.
You can't defend freedom by getting rid of it.