Lets Go Further (Alex Edwards) (Z-Library)

【One-Line Pitch】 A hands-on, start-to-finish guide to building a production-grade JSON API in Go — covering REST routing, PostgreSQL, authentication, rate limiting, and deployment. Best for developers who already know Go basics and want to ship a real backend service. 【Book Arc】 - **Opening (~0%–12%)**: Sets up the Greenlight project — a movie-management JSON API — and maps the full endpoint surface, tooling, and conventions before any code is written. - **Early (~12%–29%)**: Establishes prerequisites (Go 1.16, curl, hey, git) and the project skeleton, then stands up a basic HTTP server with configuration via flags and dependency injection. - **Middle (~29%–65%)**: Builds the core request/response layer — JSON encoding and decoding, input validation, PostgreSQL connection pooling, SQL migrations, and full CRUD operations including partial updates and optimistic concurrency. - **Late (~65%–90%)**: Layers on production concerns: filtering/sorting/pagination, structured logging, panic recovery, rate limiting, graceful shutdown, user registration, email, activation, authentication, and permission-based authorization. - **Ending (~90%–100%)**: Covers CORS, metrics, build/versioning/quality control with Makefiles, and deployment to a Digital Ocean Linux server behind Caddy as a reverse proxy. 【Key Takeaways】 - **The book is a build-along, not a reference** (Opening): every concept is introduced through the Greenlight API, so the value comes from coding alongside rather than reading passively. - **JSON handling is treated as a first-class concern** (Early–Middle): fixed-format vs. encoded responses, enveloping, custom encoding/decoding, and structured error messages are all covered in depth. - **Database work goes beyond basic CRUD** (Middle): connection pool configuration, SQL migrations, partial updates, optimistic concurrency control, and query timeouts are all addressed as production necessities. - **List endpoints need real engineering** (Middle–Late): filtering, full-text search, sorting, pagination, and pagination metadata are handled as a cohesive feature set rather than afterthoughts. - **Operational concerns are woven throughout** (Late): structured logging, panic recovery, rate limiting, and graceful shutdown appear as part of the build, not as a separate appendix. - **Authentication and authorization are distinct layers** (Late): the book separates user activation, token-based authentication, and permission-based authorization into clear stages. - **Deployment is part of the book, not an afterthought** (Ending): server provisioning, background services, reverse proxy setup, and automated migrations round out the lifecycle. - **The book assumes prior Go fluency** (Early): testing and fundamentals are deliberately omitted because they were covered in the predecessor volume, *Let's Go*. 【Reading Tips】 - **Code along from the start**: the skeleton structure, configuration pattern, and application struct are reused throughout; skipping the setup makes later chapters harder to follow. - **Deep-read the JSON and database chapters**: these contain the most transferable patterns for any Go API, not just the Greenlight project. - **Skim the deployment chapter if you already have infrastructure experience**: the Digital Ocean and Caddy specifics are useful but environment-dependent. - **Treat the appendices as a reference**: password resets, JWT authentication, and JSON nuances are supplementary and can be consulted as needed. - **Don't skip the "additional information" sections**: they contain context that isn't essential to the build but is valuable for understanding trade-offs. 【Coverage Limits】 The excerpts cover the table of contents and early-to-middle chapters in detail, but later chapters (authentication, authorization, CORS, metrics, deployment) are represented mainly by their headings; specific implementation details for those stages are not fully visible in the source material.