(2013-11-01) Winer Aws Sdk Javascript

Dave Winer sees the launch ("preview") of Amazon Web Services SDK for JavaScript as important for a grid of Single Page Application-s that can now talk to Web Service API-s without requiring centralized scaling.

*If an app running in the browser, written in JavaScript, needs to talk to a web service like Twitter, Facebook, Evernote, etc -- you have to write a server app to act as a proxy, because it's not possible for the JS code to directly call the service. This makes building an app more costly because it's more complex, but even more important, it makes it necessary to scale the app. Every user costs more money, thus forcing you to either raise money from investors or sell access to the users to advertisers.

Then a little over a year ago, Drop Box did something amazing. They basically sucked the functionality of the Proxy Server into dropbox.com, making it unnecessary to create an in-between server... And that's how we built our Fargo outliner, and that's why it performs great no matter how many people use it.

Theoretically, it (the AWS SDK) does for their web services, what Dropbox did for theirs. The claim is that you can call directly to their servers to do the kinds of things you used to need a proxy for.

I created a new bucket, s3.scripting.com, put my app in the bucket, added a CORS configuration, and ran it. *

Tech Crunch says: This means developers can now build JavaScript apps that can create and popular S3 buckets, for example, and query Dynamo D B tables without the need to access these services through any server-side code.

See related

I'm struggling to define UseCase-s for this.


Edited:    |       |    Search Twitter for discussion

No twinpages!