4 ms·

Even if there are already about twenty AWS libraries on NPM, this is a welcome addition. One nasty part of the Node.js ecosystem is the elevated risk that the o

by rgarcia 14y ago

Even if there are already about twenty AWS libraries on NPM, this is a welcome addition. One nasty part of the Node.js ecosystem is the elevated risk that the owner of a library you depend on goes AWOL. For some reason (maybe the low barrier to publishing with github + npm) this risk is incredibly high with Node.js libraries. So it's nice to see AWS put their weight behind this. It's also nice to see a language-specific library that doesn't layer on a bunch of opinions/abstractions on top of the underlying HTTP API. Makes it a lot easier to grok, debug, and leverage existing documentation. If there's anyone from AWS trolling these parts...will there ever be support for Node.js in Beanstalk?

1SaltwaterC 14y ago
Not all the owners go AWOL, especially for pieces of code that were created for the purpose of going into production. In fact, the lack of official SDK support is the actual cause of so many alternatives. For some of us, it creates a proper foundation in the long run. For example, I don't have the actual time to implement an end-to-end SDK. But hacking some code to get the job done was possible, while others found my hacks actually useful. It isn't ideal, but the World itself is far from that.
- alessioalex 14y ago
  Here's a good response from such an owner: https://groups.google.com/forum/?fromgroups=#!topic/nodejs/W4TeD_8Dyt4 https://groups.google.com/forum/?fromgroups=#!topic/nodejs/W...
  - 1SaltwaterC 14y ago
    Actually I am such an owner. I'm interested to see if the AWS SDK could be used as foundation, even though my own implementation is just a thin wrapper plus an S3 client, most of the time doing the low level plumbing (such as request signing).
mirkok 14y ago
there are quite a few people depending on aws-lib (https://github.com/livelycode/aws-lib https://github.com/livelycode/aws-lib). So maybe we could re-use the base of the official SDK but retaining aws-lib's API.

by rgarcia 14y ago

1SaltwaterC 14y ago

Not all the owners go AWOL, especially for pieces of code that were created for the purpose of going into production. In fact, the lack of official SDK support is the actual cause of so many alternatives. For some of us, it creates a proper foundation in the long run. For example, I don't have the actual time to implement an end-to-end SDK. But hacking some code to get the job done was possible, while others found my hacks actually useful. It isn't ideal, but the World itself is far from that.

alessioalex 14y ago
Here's a good response from such an owner: https://groups.google.com/forum/?fromgroups=#!topic/nodejs/W4TeD_8Dyt4 https://groups.google.com/forum/?fromgroups=#!topic/nodejs/W...
- 1SaltwaterC 14y ago
  Actually I am such an owner. I'm interested to see if the AWS SDK could be used as foundation, even though my own implementation is just a thin wrapper plus an S3 client, most of the time doing the low level plumbing (such as request signing).

mirkok 14y ago

there are quite a few people depending on aws-lib (https://github.com/livelycode/aws-lib https://github.com/livelycode/aws-lib). So maybe we could re-use the base of the official SDK but retaining aws-lib's API.