Amazon Web Services Blog: Cloudbursting - Hybrid Application Hosting (24)
share
digg
by
AWS Editor (136)
on
Hacker News (1758)
1 month, 2 weeks
ago
permalink
I get to meet with lots of developers and system architects as part of my job. Talking to them about cloud computing and about the Amazon Web Services is both challenging and rewarding. Cloud computing as a concept is still relatively new. When I explain what it is and what it enables, I can almost literally see the light bulbs lighting up in people's heads as they understand cloud computing and our services, and what ...
-
mndoci said:
Eventseer on the AWS Blog
Amazon Web Services Blog: The Emerging Cloud Service Architecture (5)
share
digg
by
AWS Editor (136)
on
Amazon Web Services Blog (131)
1 month, 2 weeks
ago
permalink
I'm going to go out on a limb today and try to paint a picture of where some of this cool and crazy cloud-based infrastructure may be going. While none of what I will write about is idle speculation, it is based on just a few data points, and may be totally off base. However, I do get to talk to plenty of entrepreneurs and developers on a daily basis, and I am starting to ...
-
Gary Burge said:
This is an intelligent analysis of the future of "the cloud".
White Paper on 'Cloud Architectures' and Best Practices of Amazon S3, EC2, SimpleDB, SQS (4)
share
digg
by
AWS Editor (136)
on
Amazon Web Services Blog (131)
2 months, 4 weeks
ago
permalink
I am very happy to announce my white paper on Cloud Architectures is now ready. This is one incarnation of the Emerging Cloud Service Architectures that Jeff wrote about a few weeks ago. If you are new to the cloud, the first section of the paper will help you understand the benefits of building applications in-the-cloud. If you are using the cloud already, the second section of the paper will help you to use the ...
Taking Massive Distributed Computing to the Common Man - Hadoop on Amazon EC2/S3 (3)
share
digg
by
AWS Editor (136)
on
Amazon Web Services Blog (131)
7 months, 2 weeks
ago
permalink
Not so long ago, it was both difficult and expensive to perform massive distributed processing using a large cluster of machines. Mainly because: It was difficult to get the funding to acquire this 'large cluster of machines'. Once acquired, it was difficult to manage (powering/cooling/maintenance) it and we always had a fear of what-if the experiment failed and how would one recover the losses from the investment already made. After it was acquired and managed, ...
