Feeds:
Posts
Comments

Posts Tagged ‘amazon’

I have been rather gung-ho about AWS and the great people behind it.  So why would I complain?
I am not – it’s just that I’d like a good thing be even better. So here goes. 
  1. A combination of Amazon Flexible Payment System and SimpleDB that is a user account subsystem with payments, pluggable into any web app.  This would be called something like Amazon Web Accounts Management .  It would have skeleton web pages for a user to signup, would automatically validate via email and would then set up a user account.  The user would pick a subscription model or one time payment or …  Just one more scalable infrastructure service I wouldn’t have to build.  Final part of this would be a layer so that users signed up by my app would use my AWS account for access without needing their own AWS account, but I would get periodic billing reports broken down by user and app.
  2. A suite of slick Ajaxy web apps running locally on my desktop/laptop to manage all my AWS services.  The key is to make them local, so I can use my AWS keys without having to upload them to every web service.
  3.  Alternately, an extension to OAuth that uses my AWS keys off my local machine and can login to 3rd party services that keep asking for my keys.
  4. Sorting and grouping on SimpleDB result sets. Sadly currently missing.
  5. Amazon should work with 37signals (Bezos funded them didn’t he?) to create a full fledged set of Rails plug-ins that provide no-compromises support for AWS.
  6. A uniform RESTful approach across all the apps, have some internal standards for consistency across S3, EC2, SimpleDB, SQS API’s at least.  All the confusion around why SimpleDB API is not RESTful and all the noise around that detracts from the bigger issues of what SimpleDB is and how to use it.  Commit to the RESTafarian religion, do your API-tithing, say your GET/PUT/POST/DELETE mantra daily and move on.
  7. A secure data API, so that service providers who use AWS can let enterprise customers know their data is secure.
  8. “Telegraphing” of intentions when you are about to meter something previously not metered – e.g. per-request charges on S3.  This prevents  people’s business models from getting whipsawed – typically for a major change like this a 6 month warning would be really great.
  9. Finally,  bulk pricing of S3 storage and transfer for people willing to buy in Terabytes.  There are data warehousing and business intelligence use cases for social data which work very well on Ec2 extra large images, along with S3, except that storage and transfer charges,  for say 10Tb,  get prohibitive.  Desktops now have TB’s – the age of the GB disk is passing – please have steeply discounted charges for the TB user.

    Read Full Post »