Slashdot Mirror


The Amazon Technology Platform

Don420 writes "Jim Gray has an interview with Amazon CTO Werner Vogels for ACM Queue. It is filled with a lot of details about the Amazon architecture that we have not seen before: 'If you hit the Amazon.com gateway page, the application calls more than 100 services to collect data and construct the page for you.' But also quite a strong statements about developing software at Amazon: 'Developers of our services can use any tools they see fit to build their services. [...] Whatever tools are necessary, we provide them, and then get the hell out of the way of the developers so that they can do their jobs. [...] Developers are like artists; they produce their best work if they have the freedom to do so, but they need good tools.'"

12 of 109 comments (clear)

  1. 100 Services ? by jonv · · Score: 3, Insightful

    'If you hit the Amazon.com gateway page, the application calls more than 100 services to collect data and construct the page for you.'

    and this a good thing ?

    1. Re:100 Services ? by shmlco · · Score: 4, Informative

      Ever considered the amount of data that has to be churned through to build your average custom My Yahoo home page? Especially one with a ton of custom news items, stocks, local weather, local movie listings, and so on?

      Major web sites are just a "little" more complex than your typical iWeb home page...

      --
      Any sect, cult, or religion will legislate its creed into law if it acquires the political power to do so.
  2. Unlimited budget by DonCarlos · · Score: 4, Funny

    Having unlimited development budget is definitely THE good thing I sometimes miss myself ;)

    --
    Marcin
  3. Sounds (almost) too good to be true... by allanj · · Score: 5, Interesting

    I wonder if the actual developers/coders see it that way themselves. Sadly, CxO's often have a warped view of how things work "on the floor".

    --
    Black holes are where God divided by zero
  4. But they need good tools by wysiwia · · Score: 3, Informative

    Sure anybody need good tools to produces something exceptional. But what can you do if the needed tools aren't available? What can developers do if they aren't happy with their tools or their environment?

    For users the answer is easy, they simply switch to something different, but for developer it's not. You usually first have to get a lot of knowledge which needs time. But one does never get more time!

    So developers have to think in advance sometimes several years. This means constantly be on the edge of the available knowledge. Tools can certainly help but nothing prevents you from getting the knowledge in advance.

    O. Wyss

    --
    See http://wyoguide.sf.net/papers/Cross-platform.html
  5. Artists? by should_be_linear · · Score: 5, Funny

    Well *Some* developers are like Artists, others are more like Naïve painters with unlimited budgets for colors and huge canvases.

    --
    839*929
  6. Tools are all well and good... by dtsazza · · Score: 3, Interesting

    ...but at the end of the day it's the developer's talent and experience that tell most of the picture. It sounds like Amazon do let their developers decide (to a large extent) how their products are going to work.

    The transition from the monolithic Obidos to the current SOA makes me wonder how exactly that part of the system works. Though it's not (that I could see) explictly stated, it certainly seems that adding scalability was a long and painful process. Planning for future developments like this is something that developers tend to be much better at than managers - so I wonder whether the developers didn't think about including scalability hooks in their initial efforts, whether they decided (back in the early days) that it wasn't worth it, or whether they wanted to but were told not to bother.

    All said, I do applaud the public stance that Vogels is taking in his attitude. If more CxOs shared it, we'd likely have beeter-designed systems all over the shop. You hire the developer because (s)he's good at developing - so let them go to it!

    --
    My, that was a yummy potato!
  7. Re:Good Tools? by mahangu · · Score: 3, Informative

    There is an idiom in my native tongue of Sinhala for this - natanna bari minihata polova adai, which translated directly (albeit a little clunkily) reads the ground is always uneven for the person who can't dance.

    Having said this, I'm sure everyone agrees that a certain amount of tools are necessary to be productive. All in all though, I think this article sums up the value of tools pretty well.

  8. My question is by Aceticon · · Score: 4, Interesting

    Developers of our services can use any tools they see fit to build their services.

    I wonder how they avoid the maintenance nightmare which is having multiple application components done using various obscure technologies/tools and the person that did it leaving the company and somebody else having to maintain/extend those application components?

    Do they standardize their build tools, require good documentation on the service implementations or just overwork the poor sods that have to do maintenance to death?

  9. Re:Thanks by stlhawkeye · · Score: 3, Insightful
    Or maybe I got you wrong and you meant that developers are like artists: Poor, starving, living for their work and only valued once they are no longer available.

    Move away from the coasts. I make $75,000/year working 40 hour weeks. I'm not on-call, have flex hours, get 3 weeks of vacation, and unlimited sick time. Quit working for IT sweat shops. Move somewhere where family time is valued and it's impossible to hire people unless you are willing to give them that flexibility. I've been through four employers in the St. Louis area and been able to land jobs with a deal akin to this one at all four. Developers are "poor"? No. Elementary school teachers are "poor." Starting salary for a developer in a low-watt market is close to $40K without a degree. That's not "poor." That's not starving, and that's not living for their work, unless by "living for their work" you mean that you're expected to show up on time and do your job.

    --
    "I have never won a debate with an ignorant person." -Ali ibn Abi Talib
  10. Re:Much use of Haskell and SML. by Fnord · · Score: 3, Interesting

    I worked at amazon for two years. I never saw any use of Haskel, SML or any other functional language. 90% of all work at amazon is some combination of C++ and Perl, with a few groups trying to transition to Java.

  11. Re:Recruiting interview? by AuMatar · · Score: 3, Interesting

    Wow, troll much? Working at Amazon currently, I'll comment on a few of these things:

    1. Low pay - it's a great place for budding "artists" fresh out of school to build "experience" that has to be unlearned at a more organized shop.

    Not at all. I'm making 15% more here than I did at HP last year. I make more than devs with equal experience at MS. The pay is pretty good.

     
          2. Dot-Com mentality - Lots of excuses for your desk being a door on two filing cabinets as well as the lack of organization.


    THe door desk is aq culture thing. THere's a whole story behind it. Think of it like a tradition a sports team has. In the end, it works well- its not pretty, but its sturdy and does its job.


          3. Turnover rate - as soon as people get experience, they leave for better paying jobs; Amazon is *always* hiring.


    Amazon is also growing- we have more developers than the year before. Yeah, there's turnover. Welcome to the IT industry- its rare for anyone to work at 1 place for more than 3-4 years. A lot of it is people staying just long enough to vest their stock grant (thats right, our sign on bonus is a grant, not an option) and then leave for another bonus elsewhere. Moneywise its the smart thing to do at any company.

    --
    I still have more fans than freaks. WTF is wrong with you people?