check it Out। I proposed Douglas as my 1st Panel speaker. I will invite Joel Webber next.
Velocity 2008 Call for Participation
Submitting a proposal is a two stage process. First, enter the proposal details on this page. After submitting these, you will then be asked to input the speaker details.
Web 3D: Distributed Database Dashboards
Proposal title *
The Solution is to re-architect our Clusters to reflect the reality that Server Client Architecture of Web 1.0 is DEAD!!! we no longer have the majority of our users coming from dumb terminals as clients. In fact most of the users are on Broadband enabled platforms with Processors, RAM & Serving Capabilities that are on PAR with the commodity hardware used by Google & Amazon, the industry leaders in Web-hosted (In the Cloud) Software as a Service . We must take this architect to its Logical Next Step. We Must Distribute the Web Applications to the shared OS of the Clients Browsers. With support in HTML 5 for "local" SQL databases ( http://webkit.org/blog/126
& the move to SQL-lite databases driven Local Applications by Adobe (FLEX & AIR) & Google (Gears), leads us to an Architecture where the Users data is served in SQL-lite Datastores in their devices browser caches (Apple Iphones use of Data URLs to avoid having to access the File systems) or Virtual Machines & Virtualization of OS's to collaboratively processed in a SETI@Home Architecture that allows users to contribute resources to the Performance of their Web Applications. You can use in-memory microsecond databases like Sleepy Cat (the Opensource version of Oracle Times Ten) to do session management of these Distributed Database Dashboards.
Practices Presentation http://googlewebtoolkit
Hi guys i will give you the architectural Scoop (I was at their meetup monday night on the Amazon.com & EC2 Meltdown Friday along with how Web D3 solves this problem @ the Super Happy Dev house today (after 1pm). Rich of unitedlayer.com & Robert F come or have & you & your servepath.com friend call me (cell 510-978-9472) to Outline the hosting opportunity for Opensocial Superviral Apps when EC2 took Twitter Down & Meetup.com has been having hockey stick problems this week and Blackberry was down Monday.I am emailing you a taste;-) I will feed you the rest in person or over the phone...
Why S3 failed
February 16, 2008
Late last night, Amazon issued a statement explaining the cause of the problem that hobbled its S3 storage system yesterday morning. It was not a hardware failure. Rather, the service's authentication system, which verifies the identity of a user, became overloaded with user requests. As one person explained to me, it amounted to a kind of accidental DDoS (distributed denial of service) attack, and Amazon didn't have enough capacity in place in one of its data centers to handle the surge.
Here's Amazon's explanation:
Early this morning, at 3:30am PST, we started seeing elevated levels of authenticated requests from multiple users in one of our locations. While we carefully monitor our overall request volumes and these remained within normal ranges, we had not been monitoring the proportion of authenticated requests. Importantly, these cryptographic requests consume more resources per call than other request types.
Shortly before 4:00am PST, we began to see several other users significantly increase their volume of authenticated calls. The last of these pushed the authentication service over its maximum capacity before we could complete putting new capacity in place. In addition to processing authenticated requests, the authentication service also performs account validation on every request Amazon S3 handles. This caused Amazon S3 to be unable to process any requests in that location, beginning at 4:31am PST. By 6:48am PST, we had moved enough capacity online to resolve the issue.
An anonymous correspondent yesterday sent me a copy of the following email that was supposedly sent to some of the company's staff from one of Amazon's top technical executives (AVS refers to the authentication system):
Sent: Friday, February 15, 2008 9:18 AM
Subject: RE: WTF
My three "Why The Fuck" questions :
1. How come a single EC2 customer can generate so much load on AVS that it renders it inaccessible for all other customers.
2. Why didn't the monitoring on AVS alarm catch this earlier?
3. Why is it that we still do not have a better communication plan towards our customers. For a company that proud [sic] itself on its customer focus we are doing an abysmal job here.
I didn't post this yesterday because I couldn't verify its accuracy. But given that it seems to be backed up by the official explanation, I feel comfortable posting it now. Still, it's unconfirmed information. I have asked Amazon whether it's a real email and am awaiting a response. (I hope it's real - this is exactly the kind of visceral email you want to see an exec shoot out in these circumstances.)
Amazon promises quick action to ensure the problem doesn't happen again and that users are supplied with better information on system status:
All in all, I think Amazon has handled this outage well. The problem revealed some flaws in Amazon's otherwise highly reliable system, including shortcomings in its communications with users, and the company will make important improvements as a result, to the benefit of all its customers. These kinds of small but embarrassing failures - the kind that get you asking WTF? - can be blessings in disguise.
As we said earlier today, though we're proud of our uptime track record over the past two years with this service, any amount of downtime is unacceptable. As part of the post mortem for this event, we have identified a set of short-term actions as well as longer term improvements. We are taking immediate action on the following: (a) improving our monitoring of the proportion of authenticated requests; (b) further increasing our authentication service capacity; and (c) adding additional defensive measures around the authenticated calls. Additionally, we've begun work on a service health dashboard, and expect to release that shortly.