Redis in Action (Josiah L. Carlson) (Z-Library)

【One-Line Pitch】 A hands-on, example-driven guide to Redis that takes you from the five core data structures to building real-time web features, caching layers, and scalable deployments—ideal for developers and sysadmins who want to solve practical problems with an in-memory database. 【Book Arc】 - **Opening (~0%–9%)**: Introduces Redis as a fast, open-source, in-memory key-value store. The author sets the tone: this is a practical book for "getting things done," not a sterile API reference. It outlines the book's three-part structure: basics, commands/administration, and scaling. - **Early (~9%–28%)**: Covers the five fundamental data structures—STRINGs, LISTs, SETs, HASHes, and ZSETs—with console examples. Builds a complete article voting and aggregation site to demonstrate how these structures work together, introducing commands like SADD, ZINCRBY, and HINCRBY. - **Early (~28%–38%)**: Moves into web application patterns. Shows how to manage user sessions, implement a shopping cart, and build a page caching layer. Includes a crucial lesson on memory management: caching everything can exhaust RAM, so you need strategies like token cleanup and scheduled re-caching. - **Middle (~38%–47%)**: A deep dive into Redis commands, organized by data type. This section is a practical reference for the 95% of commands you'll use in real applications, including blocking list operations (BLPOP/BRPOPLPUSH) for messaging and advanced HASH operations like HINCRBYFLOAT. - **Middle (~47%–end of excerpts)**: Explores sorted sets (ZSETs) in detail and introduces the publish/subscribe (pub/sub) pattern. The excerpts show how ZSETs store member-score mappings for ordered data, and how pub/sub enables real-time messaging between clients. 【Key Takeaways】 - **Redis is a problem-solving tool, not just a cache** (Early): Its unique combination of being in-memory, remote, persistent, and scalable lets you build solutions beyond simple key-value lookups. The book's goal is to shift your thinking from "tables and rows" to "which Redis structure fits best." - **Five data structures form the core** (Early): STRINGs, LISTs, SETs, HASHes, and ZSETs each have distinct semantics. ZSETs are unique to Redis and are invaluable for maintaining ordered data like leaderboards or time-based rankings, as shown in the article voting example. - **Real-time thinking is the default** (Early): Almost every example in the book solves a problem in real time, except for task queues. This mindset helps you design for immediate data updates and low-latency responses. - **Memory is a finite resource that needs active management** (Early): The web application chapter demonstrates that caching every page can exhaust RAM. Solutions include cleanup functions that remove old session tokens and scheduled re-caching of inventory data, showing that "cache everything" is rarely the right answer. - **Commands are the building blocks for your own solutions** (Middle): Chapter 3 is a command reference organized by structure. It covers blocking pops for queues, HASH bulk operations, and sorted set commands, giving you the vocabulary to implement patterns like messaging and task queues. - **Publish/subscribe enables real-time communication** (Middle): Redis's pub/sub feature allows clients to subscribe to channels and receive messages instantly. This is useful for scenarios where you need to push updates to multiple listeners, such as live feeds or notifications. 【Reading Tips】 - **Skim the command tables in Chapter 3**: You don't need to memorize every command upfront. Use this chapter as a reference when building your own applications, and focus on the examples that show how commands combine to solve problems. - **Deep-read the article voting example in Chapter 1**: This is the foundational case study that ties all five data structures together. Understanding it will make later chapters on web applications and scaling much easier to follow. - **Pay attention to the "why" behind each pattern**: The author often revisits earlier solutions to improve them. Note where these callbacks occur, as they teach you how to evolve your own designs. - **Use the provided test runners**: The book includes source code with test runners for each chapter. If an example is confusing, running the tests will show you exactly how each function is used. - **Don't get stuck on Python specifics**: All examples are in Python, but the focus is on Redis commands and logic. If you're not a Python developer, translate the command sequences to your language of choice. 【Coverage Limits】 The excerpts cover the book's introduction, core data structures, web application patterns, and a substantial portion of the command reference. They do not cover later chapters on data persistence, replication, sharding, Lua scripting, or advanced administration topics.