Building and Deploying WebAssembly Apps Building secure, portable, and optimized web applications with WebAssembly (Peter Salomonsen)（Z-Library）

【One-Line Pitch】 A hands-on tour of WebAssembly as a universal binary format—not just for browsers but for servers, desktop audio tools, blockchains, and Kubernetes. Best for developers who already know one of C/C++, Rust, or TypeScript and want to see Wasm applied to real, non-toy projects. 【Book Arc】 - **Opening (~0%–10%)**: Frames the core motivation—a portable, compact binary that doesn't sacrifice performance—and situates Wasm in the lineage from browser plugins and asm.js to today's multi-platform use. Introduces the author's real-world projects (WebAssembly Music, Wasm-Git, NEAR contracts) that anchor later examples. - **Early (~10%–30%)**: Builds low-level fluency. You meet the WebAssembly Text (WAT) format for hand-manipulating bytecode, then AssemblyScript for fast in-browser compilation, then optimization tooling (LLVM, wasm-opt, wasm-metadce) and memory-management trade-offs. - **Early–Middle (~30%–45%)**: Language compilation and porting. Emscripten brings C/C++ to the web (build automation, Asyncify, WASI comparison), and the libgit2 port shows a full-stack offline-capable app with browser storage, commits, and remote sync. - **Middle (~45%–60%)**: Extends Wasm beyond the browser into audio plugins and asynchronous patterns—callbacks, Asyncify, shared memory and atomics, and JavaScript Promise Integration for pausing/resuming execution. - **Late (~60%–80%)**: Runtimes and WASI. Explores server-side runtimes, the Component Model for combining modules in different languages, serverless request handlers, and embedding Wasm inside native desktop apps. - **Ending (~80%–100%)**: Applied deployment. Smart contracts on NEAR (from minimal WAT to Rust and embedded JavaScript), then WebAssembly on Kubernetes—containers, scale-to-zero, and an AI image-classification service. 【Key Takeaways】 - **Wasm is a universal binary, not a web-only technology** (Opening): the book's central thesis is that the same compact, portable format serves browsers, servers, desktops, and blockchains—so you should read it as a platform book, not a frontend book. - **Reading WAT pays off even if you never hand-write it** (Early): manipulating the text format is shown to be more efficient than recompiling when updating embedded JavaScript or toggling synthesizer features. - **Language choice is a real decision, not a formality** (Early): AssemblyScript offers rapid in-browser compilation and a high-level feel with low-level control; C/C++ via Emscripten suits legacy porting; Rust fits performance and safety needs. - **Optimization is a first-class skill with concrete tooling** (Early): LLVM flags, wasm-opt, and wasm-metadce are presented as practical levers, alongside the speed-vs-size trade-off and the cost of calling JavaScript math host functions. - **Porting legacy code is a repeatable workflow** (Early–Middle): the libgit2 case demonstrates build automation, filesystem emulation, and replacing TCP networking with browser APIs to produce an offline-first app. - **Blocking code breaks event-driven runtimes** (Middle): the async chapter explains why synchronous Wasm functions stall a runtime and surveys callbacks, Asyncify, shared memory/atomics, and Promise Integration as remedies. - **WASI and the Component Model unlock composition** (Late): runtimes like WasmEdge and WASI Preview 2 let modules written in different languages be combined and embedded in native applications. - **Wasm's sandbox maps naturally onto cloud and blockchain** (Ending): the same isolation properties support NEAR smart contracts and Kubernetes-hosted services that scale to zero. 【Reading Tips】 - **Deep-read the WAT and optimization chapters** even if you plan to stay in a high-level language; they explain why binaries behave the way they do and make later debugging far easier. - **Skim the publishing/front-matter and reviewer bios**—they carry no technical content and can be skipped entirely. - **Treat the case studies as templates**: when you hit libgit2, NEAR, or the Kubernetes AI service, extract the workflow (build → port → integrate → deploy) rather than memorizing project specifics. - **Pick your language track early**: if you're a TypeScript developer, follow AssemblyScript; if you're porting existing code, follow Emscripten; if you're performance-focused, follow Rust. - **Keep the async chapter bookmarked**—it's the hardest conceptual stretch and the one most likely to bite you in real deployments. 【Coverage Limits】 The excerpts are heavily front-loaded with front matter, table of contents, and chapter introductions; detailed code, exercises, and the full body of later chapters are only partially represented, so this guide maps the book's structure and themes rather than its step-by-step implementations.