On Wed, 2007-01-17 at 10:55 -0800, Bob La Quey wrote: > Is anyone playing with Amazon Web Services (AWS) > See http://tinyurl.com/2ajud6 > Or for those who like the long url here is the 137 character version :) > http://www.amazon.com/AWS-home-page-Money/b/ref=sc_fe_l_1_3435361_1/002-2104490-6212057?ie=UTF8&node=3435361&no=3435361&me=A36L942TSJ2AJA > > The heart of the matter is their Solutions Catalog > http://solutions.amazonwebservices.com/connect/index.jspa > > Using AWS would be near the extreme end of a continuum of > approaches that runs from rolling and running everything > oneself through farming it "all" out. > > What I am wondering is this. What are the architectures that > leverage what AWS is doing well but add unique glue > (or interfaces) so as to allow one to make use of their scale > and incrementality? > > Does something like this make sense? >
Personally, I don't like the idea of farming anything out, especially if we (meaning the company that needs the new service) have the skills internally to develop and maintain it. Some of the reasons I feel this way are because it makes us beholden to the company we've farmed it out too, we have to continue to pay them, we are limited in upgrade options, changes, enhancements, etc., and we are trusting someone else with our data. In the next few weeks I'll be getting back to our new web site development here at QUAKE. I have the new server here at my desk all ready to have Apache, Tomcat, MySQL DB support files, and Java installed on it. This will provide an automated Customer Support area for our web site, including the possibility of e-Commerce. The final reason, which has no bearing on the decision at all, is that it takes the fun out of my job because I don't get to develop it. :D PGA -- Paul G. Allen BSIT/SE Owner/Sr. Engineer Random Logic Consulting www.randomlogic.com -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
