path: root/blog/entry/awsdownapr11.mdwn
diff options
authorSean Whitton <>2015-11-18 10:09:12 -0700
committerSean Whitton <>2015-11-18 10:09:12 -0700
commitdeb4807989d127e40e44c1192477c40e30f88180 (patch)
tree41e557cc82e01b0e76de8d4f548105023af8dfee /blog/entry/awsdownapr11.mdwn
parent675d02fc2c3d2bfb53a81db6d2c55f0dfbbd79ed (diff)
imported PyBlosxom entries and comments
Diffstat (limited to 'blog/entry/awsdownapr11.mdwn')
1 files changed, 24 insertions, 0 deletions
diff --git a/blog/entry/awsdownapr11.mdwn b/blog/entry/awsdownapr11.mdwn
new file mode 100644
index 0000000..3dd33c3
--- /dev/null
+++ b/blog/entry/awsdownapr11.mdwn
@@ -0,0 +1,24 @@
+[[!meta date="2011-04-22 09:26:00"]]
+[[!meta title="Info on why Amazon's AWS being down is so catastrophic"]]
+[[!tag imported_PyBlosxom tech cloud]]
+[AWS is down: Why the sky is falling | justinsb's
+This is a really interesting read. There are two sides to the cloud
+computing lark as I see it, though I've not seen the distinction drawn
+by anyone else myself: firstly there is the really dangerous idea that
+users should store their data online with various providers who are
+probably using the second part of cloud computing but who don't have to
+be, which is really bad because it takes away control over something
+that is increasingly important in our lives. But secondly there is the
+idea of using elastic virtual instances over traditional always-on
+servers that sit idle half the time; it's more efficient and
+environmentally friendly.
+The problem is that AWS doesn't really have much competition in the
+latter atm which is why it going down brings the web with it which is
+bad. I think that this also shows that traditional websites offering
+information should definitely keep running their own webservers; such
+sites at ten times more important than Web 2.0 and its friends and need
+to remain up.