Reddit mentions: The best web services books

We found 8 Reddit comments discussing the best web services books. We ran sentiment analysis on each of these comments to determine how redditors feel about different products. We found 3 products and ranked them based on the amount of positive reactions they received. Here are the top 20.

🎓 Reddit experts on web services books

The comments and opinions expressed on this page are written exclusively by redditors. To provide you with the most relevant data, we sourced opinions from the most knowledgeable Reddit users based the total number of upvotes and downvotes received across comments on subreddits where web services books are discussed. For your reference and for the sake of transparency, here are the specialists whose opinions mattered the most in our ranking.
Total score: 20
Number of comments: 4
Relevant subreddits: 2
Total score: 3
Number of comments: 1
Relevant subreddits: 1
Total score: 2
Number of comments: 1
Relevant subreddits: 1
Total score: 1
Number of comments: 1
Relevant subreddits: 1
Total score: 1
Number of comments: 1
Relevant subreddits: 1

idea-bulb Interested in what Redditors like? Check out our Shuffle feature

Shuffle: random products popular on Reddit

Top Reddit comments about Web Services:

u/mdaffin · 3 pointsr/webdev

How do you get a list of all your subscriptions? Why not have a /subscriptions/ endpoint which you can get, post, put and delete to like the articles to manage your subscriptions. If you want an admin user or article author to manage subscriptions to their articles you could also have /articles/1/subscriptions/ or add a filter to the /subscriptions/ endpoint.

As for login - it is not really a resource so does not really have to follow the rest API as strictly. Posting to a login/logout/signup endpoints is fine as these don't tend to get unmanageable and tend to follow different usage patterns in general.

---

There are lots of different ways to do things with restful APIs as there is no proper standard but there are a whole bunch of best practices on how to design restful API, most of which say the same things but sometimes contradict each other on the finer details or ignore the more hairy side of designing rest APIs.

Generally, all these have the aim of creating nice usable APIs, so as long as you are able to do that I would say it does not matter so much how the API is designed or if it is completely restful or not. But the best practices are there for a reason and it is worth understanding why if you want to go against them so you know what trade off you are making.

There are quite a few book on the topic such as Build APIs You Won't Hate that are worth a read if you want to get better at API design.

u/cddotdotslash · 2 pointsr/aws

Hopefully I can provide some help!

  1. The IAM role that you give Lambda does need CloudWatch permissions (put logs, create log groups, create log streams). When you test it on the Lambda page, they display it right there, but for other invocations, it needs those IAM permissions.

  2. Not directly, but once the logs show up in CloudWatch, I believe you can click on the group and then stream them to Kinesis. From there, you can copy them to S3 I think. If not, you can setup another Lambda function to poll the group, download the logs and copy them to S3. A bit roundabout, but that's all we get for now.

  3. Yes, from what I understand, the container hosting the function assumes the IAM role just like EC2. So if someone managed to get control of it, they'd have those same permissions.

  4. Nothing specific, but definitely make sure that you always exit the function using the context.succeed or context.fail methods. With Node's callbacks, it's very easy to miss these and then you'll pay for the full execution time until it gets killed for timeout.

  5. This is something I hate. You can't regex the JSON. So for now (AWS has this on their radar according to some forum posts), I just fail with a string. You can then use an API Gateway mapping to send back actual JSON.

  6. This I'm not too sure of. Pretty much anything that runs on Node will run in Lambda, so if you have a module you like, that should work. One thing to keep in mind though is that if you miss an error, Lambda and the API Gateway will send the whole stack trace back. Kind of a bad thing to send to users.

    Good luck with the service! I'm a big fan, but it definitely needs some more work from AWS. It's so difficult to setup hundreds of routes since every one needs to be configured individually.

    Also, shameless plug, but if you're interested in Lambda, I wrote a whole eBook about it. You can pre order it now, but it'll be out on January 11th.
u/leptons · 1 pointr/aws

Your expertise is questionable, and no longer of any interest to me.

Maybe you should go educate yourself: http://www.amazon.com/AWS-Lambda-Guide-Serverless-Microservices-ebook/dp/B016JOMAEE