Django for APIs: Build web APIs with Python & Django (英語) ペーパーバック – 2018/6/15
Kindle 端末は必要ありません。無料 Kindle アプリのいずれかをダウンロードすると、スマートフォン、タブレットPCで Kindle 本をお読みいただけます。
Learn how to build web APIs with Python and Django 2.2.
Take a modern API-first approach to creating 3 different Django back-ends: a Library API, Todo API, and a Blog API with user authentication, permissions, proper documentation, and more. You'll even learn how to connect them to a React front-end for a truly full-stack web application.
TABLE OF CONTENTS
- Chapter 1: Web APIs
- Chapter 2: Library website and API
- Chapter 3: Todo API
- Chapter 4: Todo React Frontend
- Chapter 5: Blog API
- Chapter 6: Permissions
- Chapter 7: User Authentication
- Chapter 8: Viewsets and Routers
- Chapter 9: Schemas and Documentation
1件中1 - 1件目のレビューを表示
* Better beginner resource than official docs and other books
* Up-to-date (mine was printed on the same day that I ordered the book)
* Quick read (went through it in just a few days)
The Full Review:
When I first started to play around w/ python I remember setting up an API by following DRF's quickstart. It worked. I set an API up but I couldn't do anything w/ it. I didn't understand what was going on or what had happened behind the scenes to get this app up and running. Going through the rest of the official documentation, I realized that it's meant for people who are comfortable w/ Python and are VERY comfortable w/ Django. But if you haven't had a chance to build several production projects where you've installed and successfully configured 3rd party apps, the official tutorial can be hard to follow.
I've since had the opp to play around w/ Django a bit. I've built a few real-life apps w/ it. About a month ago I reached a pt where I needed to implement an API for one such project. I revisited the official tutorial but while I understood a lot more this time, I still felt somewhat lost.
I decided to follow an e-book that I got a few months back as part of an e-book bundle purchase I made. Everything was going great until chapter 2 when the code presented didn't work. I found that the number one complain for that book was errors in code. No good.
Searching for a DRF-specific book, I this book. I have Vincent's "Django for Beginners" book and I've found it to be the best resource for DJango by far. Knowing that I liked his way of teaching and his way of writing, I went for this book instantly. Didn't even bother to read the reviews.
The first thing to note about this book is that it is up-to-date. How new and fresh is the information in the book? The bottom part of the very last page has the print date. Mine was printed the very same day I purchased it. EVERY piece of software referenced matched the actual latest version of said software/add-on. This alone, is reason enough to purchase this book over any other.
William takes time to explain how REST works. He provides details for how requests and tokens and codes are sent back and forth from client to server. Every piece of code works and the explanation of said code is very easy to understand.
This is a quick read. Should be doable in a weekend if you've got nothing else going on. You'll be up and running a real API in no time. Better yet, you will be at a point where you can jump over to the official DRF docs. My next steps will definitely be to get a better handle on the 3rd party software used in the book (swagger, rest_auth, allauth, etc). Again, this book sets you up so that you can use all of these packages' official docs as reference... as they were intended to be used.
Buy this book if you are new to APIs, have been developing Django apps for less than a yr, or if you've set up DRF-based APIs using the official docs but still not quite sure how/why things work.
It worths the money 100%. The books also has helped me to realize that there are a lot of things that I could be doing better even with the ASP.Net Web API. I can't wait to move completely from ASP.Net Web APi to Django Rest.
My only minor, but really minor complain it's the Kindle version has to improve the code layout, because there are some coding lines that get unorganized. But other than that 5/5!!!!