NGINX Unit Cookbook (Derek DeJonghe [DeJonghe, Derek])（Z-Library）

【One-Line Pitch】 A hands-on recipe guide to NGINX Unit, the open source dynamic application server that runs polyglot apps behind a single RESTful JSON API. Best for developers, DevOps engineers, and system architects who deploy and route web applications and want to cut middleware sprawl. 【Book Arc】 - **Opening (~0%–10%)**: Frames the problem — polyglot microservices multiply middleware servers — and introduces Unit's layered architecture (controller, router, isolated app processes) and API-driven reconfiguration. - **Early (~10%–35%)**: Installation across ecosystems: source builds, Red Hat/yum, Debian/apt, plus Go and Node.js module packages, with language-version caveats. - **Middle (~35%–55%)**: Core configuration objects — application, listener, and route — covering JSON structure, match/action routing, named routes, and evaluation order. - **Late (~55%–85%)**: Applying configuration in practice: serving applications, routing requests, security and application isolation, and integration with common web languages and ecosystems (excerpts thin here). - **Ending (~85%–100%)**: Consolidation and operational integration — using Unit's API to drive change from the application layer over static infrastructure (excerpts do not cover specifics). 【Key Takeaways】 - **Unit is a dynamic application server, not just a web server** (Early): it reconfigures at runtime without dropping connections, unlike restart-based middleware. - **One middleware for many languages** (Early): compiled and scripting languages — Node.js, Go, JSP, PHP, Perl, Python, Ruby — share a unified configuration, reducing operational complexity. - **Architecture separates concerns** (Early): a controller process manages config, a router process queues connections asynchronously, and each app runs in isolated processes. - **Configuration is API-first and RESTful** (Early): the controller is exposed over Unix or TCP sockets using REST paths, methods, and JSON bodies, enabling remote and automated management. - **Three JSON object types form the foundation** (Middle): application objects define runtime characteristics, listener objects bind IP/port to targets, and route objects handle matching and dispatch. - **Routing is ordered and expressive** (Middle): route steps evaluate in sequence with first-match wins; match options (host, uri, method, scheme, headers, cookies, etc.) combine as AND, while arrays act as OR. - **Installation paths vary by platform** (Early): official repositories for RHEL-like and Debian systems, or source builds with per-language modules configured and installed separately. - **Unit suits migrations and DevOps workflows** (Early): its API and dynamic nature let teams standardize middleware and drive change from the application layer. 【Reading Tips】 - Read Chapter 1 closely for the "what and why"; it is the only narrative section before the book shifts to cookbook format. - Skim installation recipes for your specific OS and language modules — treat them as reference, not linear reading. - Deep-read the configuration chapter (application, listener, route objects); this is the conceptual core you will reuse constantly. - Keep the companion code repository handy and run examples rather than reading them passively. - Note version caveats: language module availability differs across OS versions, so verify against your target system. 【Coverage Limits】 This guide is based on stratified excerpts covering the introduction, installation, and configuration-object chapters; later material on security, isolation, and language-specific integration is only lightly represented, so those areas are summarized at a high level.