So perhaps the biggets down-side (and I hope not the Achilles tendon) of Amazon EC2 is the lack of persistent storage ... out of the box.

Your data will be lost if your instance crashes. What are the odds? It depends on Amazon's reliability I suppose -- but also how clean you keep your server instance. Or even perhaps how many people hit your site that might cause some sort of instability. Maybe??

Anyway. There are persistent storage options through third party sources and Amazon is going to be providing persistent storage for EC2 soon which may make all this moot.

There are two big options that you have right now and with them you can mount an S3 partition like it was a physical local drive on an EC2 instance. It works quite well. There's ElasticDrive and PersistentFS.

I'll be comparing the two here soon. I have used ElasticDrive, and I'm going to use PersistentFS next. Differences? From what I can tell, slight and maybe they don't even matter for most users. There's a forum thread here where the two kinda duke it out. There's also this forum thread where I was asking a bunch of questions and very kindly someone at PersistentFS was very on top of everything. Perhaps that thread got off track it was originally about Amazon offering a persistent storage solution...which would make things like ElasticDrive and PersistentFS useless? Maybe. Maybe not. Probably not in the case of mounting something other than S3...but it may not be good for them. Though the thread is now moving off to discussions about reliability and how things work. Which is nice, contrasting current web hosting standards or practices with the Elastic Compute Cloud is very interesting. 

I just hope Amazon's persistent storage solution isn't outrageous. I don't think it's fair to pay extra for it...to a degree. I would expect it to cost money for a certain amount of space...But I would also expect a certain amount of persistent storage to come with each instance based on its size. We'll see what Amazon has in store for us soon...Until then, I'm going to check out other solutions and report my findings here. 

 

So I changed up how videos are converted to FLV. I made it an action an admin needs to perform after uploading videos. I will also re-implement a cron job that can be controlled from the admin back end.

This pretty much puts the installation here on par with, if not slightly ahead of, the Minerva Blog installation. The next thing is of course to get it all setup with EC2 and load balanced/clustered. Aside from making a nice default theme to use. Can it be? A real working demo ready to show off? I sure hope. 

Well, it's back to the original task at hand now that I'm catching all up -- Working with Amazon EC2. 

Just posting to vent my frustrations about Media Temple...Thank God for EC2...It's sooooo much better. I'm unsure why so many people use Media Temple (and even more confused about why they put logos on their site like it's something trendy or to be proud of...my feelings? Fuck you, I'm paying you, you can take your logo elsewhere because you sure as hell don't do anything great for me)...

Anyway, back to more configuration issues implementing code on those stupid crummy ass Media Temple servers that works just fine on EC2 and other shared hosts like Apthost, Lunarpages, etc. PROOF (in my mind) that MT has some serious issues they need to address.

I'm getting very very tired of this layout. It's accesible, not bad, clean, and even a little different, but it's not familiar enough I fear. Not to be like everyone else out there...Or have my blog look like every other blog out there, but I need it to pop more. Maybe some enhancements/accents or interesting elements can be put into this current design to make it work...Who knows. I'll be changing it soon, I just have to migrate the rest of the tools needed to convert video and clean up some of the code. I also need to find a better solution for media players. It's just tough with such limited time.

Ok so the game plan here. This is a version of my application, Minevablog. It needs some cleaning up though. Once I get that all set, I'm going to start stress testing. Well backup...First, well, a backup. Just to be safe. After that, I'll be setting up multiple instances and setting them up to be all load balanced and clustered.

Ok once that multi-instance environment is setup, THEN I'll stress test. Probably running load testing from another instance actually. I will hammer the ever living christ out of this blog and push it. I hope I can get an instance to crash. I want to see how I can keep the site alive under extreme conditions...How I might be able to turn on more instances for support, etc. I also want to benchmark things to see how speedy everything is.  

Mmmm, exciting.