church of default

Bryan is now a Joyeur « Joyeur.

Between this and the Drizzle team leaving you can connect the dots to how Oracle is going to treat MySQL.

Its not a coincidence that in both cases the company to pickup the talent was a cloud hosting one.

Huffington Post (sorta)
Gawker
Cafe Mom
Etsy (two)
Interactive One
Shutterstock.com
ideeli
Vimeo
“An online video advertiser”
Gilte
Meetup
WNET (ok not really webops but its channel 13)
GetGlue (is that a glue huffing social network?)
Freelancers Union
terrible job ad
ZocDoc (they want a network engineer really)
Jen Bekman Projects
Some West Coast Jerks
Nature.com
LanguageMate

and thats just the last few weeks

also, check this out, its got to be a kidney harvesting scam or something
IT Team Lead (Bermuda)

I figure I should put this somewhere. I come in at 19:00.

I was just telling someone last night that as awesome as EC2 is you still can’t run a high traffic LAMP site on it because the MySQL-write-master or “1000+ IOPS block device” answer is still missing.

Then this morning Vito passed me this: High Performance Computing Hits the Cloud
Which also led me here: New Amazon EC2 Instance Type – The Cluster Compute Instance

And for a few minutes there I thought they’d finally done it and I was wrong.

But alas, no, the “cluster compute instance” which appears to be one-half of a quad-socket/quad-7200rpm-drive server is offering you just that. 2x 7200rpm sata drives. Thats maybe 150 good random IOPS, not even close :(

You could string a bunch of them together in some kind of crazy LVM on iSCSI setup but you’d probably still only wind up with something in the ~600 IOPS family you can already get with almost-as-convoluted EBS setups.

Seems like there’s two ways around this currently. Keeping stuff in-house (well, colo) so you can scale up the hardware, or having your developers rewrite everything to not depend on a single MySQL-write-master so tightly. I always bet against the option that requires devs to redo stuff.