Author Topic: Using Clouds in site development  (Read 2947 times)

grnidone

  • Inner Core
  • Hero Member
  • *
  • Posts: 1652
    • Yahoo Instant Messenger - e
    • View Profile
    • Email
Using Clouds in site development
« on: April 28, 2011, 05:47:20 PM »
I have to say, the more I look into this, the more I like it.  Host scripts or images that many people use on super fast servers and your pages fly.  I like the idea that I can use someone else's work to make my site go.

At this time, I don't see a downside to it, but I will admit that I've not used it.  I just like the idea.

http://aws.amazon.com/cloudfront/
http://www.google.com/apps/intl/en/business/cloud.html

Has anyone here used "the cloud" for development?  How has it fared?  What do you see as the advantages/ disadvantages of it?

Gurtie

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1628
    • View Profile
Re: Using Clouds in site development
« Reply #1 on: April 28, 2011, 06:17:18 PM »
amazon -

* isn't really 'a cloud' - you can't seamlessly expand as much as you want immediately for example, they make you wait for an 'upgrade' to your account.  wtf?
* gets hacked
* and goes offline for 12 hours at a time

that said, its probably better than that implies but personally I have more hassles managing pissed off clients than dealing with truculent sys admins, so I'd rather keep things in house. I guess if I had to get personally hands on with servers I would be more forgiving of 12 hour outages. The couple of things I do deal with at Amazon are non critical and only a mild irritation when access dies.

jetboy

  • Inner Core
  • Sr. Member
  • *
  • Posts: 433
  • Hens of warfare!
    • View Profile
    • Email
Re: Using Clouds in site development
« Reply #2 on: April 28, 2011, 06:31:35 PM »
Quote
Host scripts or images that many people use on super fast servers and your pages fly

While not quite cloud computed, I'd recommend that if you use common scripts, such as jQuery, you link to a CDN (content delivery network) version (http://docs.jquery.com/Downloading_jQuery#CDN_Hosted_jQuery) rather than host them yourself. If the user has visited any other site that uses the same CDN, the script will already be cached in the browser, saving them a big download on your site.

As best practice for JavaScript loading nowadays is to use an async loader such as LABjs (http://labjs.com/), you could quite easily have a backup copy locally that you could call if the CDN times out.

ukgimp

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2241
    • View Profile
Re: Using Clouds in site development
« Reply #3 on: April 28, 2011, 08:37:50 PM »
Hasn't the cloud on amazon just failed with permanent data loss?

dogboy

  • Guest
Re: Using Clouds in site development
« Reply #4 on: April 29, 2011, 04:00:53 PM »
>permanent data loss

wow, I knew they were down, but permanent data loss is kinda unheard of anymore... I guess you could say it was a real cluster f###:) heeheheh

Hey, lemme get this straight, the cloud over there is different than their special image only hosting setup?  Or is it all tied together?

ukgimp

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2241
    • View Profile
Re: Using Clouds in site development
« Reply #5 on: April 29, 2011, 10:49:46 PM »
http://technolog.msnbc.msn.com/_news/2011/04/28/6549775-amazons-cloud-crash-destroyed-many-customers-data

As a backup to my backups I like it but relying on it when the owners (eg amazon) won't actually give a f###. No thanks. Not yet.


Leona

  • Inner Core
  • Hero Member
  • *
  • Posts: 543
    • View Profile
    • Email
Re: Using Clouds in site development
« Reply #6 on: May 12, 2011, 12:49:03 PM »
I agree it is good in theory but it still has a long way to go, I used it for content delivery rather than a full build, the data served wasn't amazingly fast, infact it was just as fast as when it was placed on a shared lightspeed server, although obviously this would not be that case during traffic spikes.

However there are issues regarding leeching and hotlinking that amazon (last time I looked) hadn't provided a solution for (although there are third party solutions out there) and the interface and account management is far from user friendly which is nuts.

With that said it does provide a good, cheap solution or so I thought before the outage and data loss issues. It now seems it is not all it boasts to be, I certainly wouldn't structure my main frame around it just yet, but still worth using for content delivery and streaming that is not of huge value if hacked.
« Last Edit: May 12, 2011, 12:56:26 PM by Leona »