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.
1. Build APIs You Won't Hate: Everyone and their dog wants an API, so you should probably learn how to build them.
- O Reilly Media
Features:
Specs:
Release date | September 2018 |
2. AWS Lambda: A Guide to Serverless Microservices
- Insulated Jacket for 42" Built-In Grill
- Mandatory for grills installed in islands with combustible materials
- Attractive all welded, stainless steel exterior
Features:
Specs:
Release date | January 2016 |
3. REST APIs with Django: Build powerful web APIs with Python and Django
Specs:
Height | 11 Inches |
Length | 8.5 Inches |
Weight | 1.04 Pounds |
Width | 0.45 Inches |
🎓 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.
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.
Hopefully I can provide some help!
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.
William S. Vincent's Rest APIs with Django https://www.amazon.com/REST-APIs-Django-powerful-Python/dp/198302998X
https://www.amazon.com/REST-APIs-Django-powerful-Python/dp/198302998X
i will pay 5$ AGC for this
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