Hacker Newsnew | past | comments | ask | show | jobs | submitlogin
Using the AWS JavaScript SDK in the Browser (flippinawesome.org)
35 points by akkartik on April 30, 2014 | hide | past | favorite | 5 comments


I love AWS but I can't imagine using this over something like Parse or FireBase.

You get object storage with S3 but I'm not sure what else this SDK gets you. Not sure that's compelling enough for many pure front end developers.


You get object storage with S3 but I'm not sure what else this SDK gets you. Not sure that's compelling enough for many pure front end developers.

From the article:

    AWS DynamoDB: A NoSQL database service that allows scalability and many other features.
    AWS.SNS: A Simple Notification Service that allows push notifications.
    AWS.SQS: A Simple Queue Service that allows the creation and management of queues.
    AWS.S3: The Simple Storage Service that allows object storage and management, one of the most used services.
    AWS.STS: A Security Token Service that provides a temporary access token.


From my comment - over something like Parse or FireBase.

Parse covers DynamoDB and SNS for push notifications. And possibly files (I've never used it, so don't know for sure) [1].

Not sure the remainder is that compelling.

[1] https://parse.com/docs/data#data-types


DynamoDB? SQS? SNS?

What can't you do given access to a key-value store, object storage, and some message-passing mechanisms? Keep in mind, IAM policy is fine-grained enough to restrict access to specific keys and attributes in DDB, etc.


That's my point. Parse offers most of that and seems like a much easier way to get started.

I've never used nor am I a big fan of Parse but if you're in the market I'd imagine it Parse is geared towards front end developers more than this SDK.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: