0 views collected around this technical thread.
This article explains how Maven’s reactor determines build order in a parent‑child multi‑module project and demonstrates how to use command‑line options such as -pl, -rf, -am, and -amd to build only required modules or their dependents, greatly speeding up the build process.
This article introduces Spring WebFlux, a reactive web framework introduced in Spring 5, explains the concept of reactive programming, compares it with Spring MVC, describes its concurrency model, and provides practical code examples for building a WebFlux application with Spring Boot.
This article introduces Spring WebFlux as a reactive, non‑blocking web framework for Java, explains the concepts of reactive programming, compares it with Spring MVC, and provides practical code examples—including Mono/Flux usage, routing, and handlers—to help developers build and run a WebFlux application with Spring Boot.
The article shows how a unified abstraction called statefulMap, together with a resource‑aware mapWithResource primitive, lets developers implement a wide range of complex reactive‑stream operators—such as buffering, indexing, deduplication, and safe DB access—in a concise, composable, thread‑safe manner, dramatically reducing boilerplate code.
This article explores the use of Reactor in Spring Cloud Gateway, highlighting its role in enabling reactive programming for efficient API gateway implementations through non-blocking, asynchronous operations and advanced data flow management.
This article introduces Spring WebFlux, explains reactive programming concepts, compares it with Spring MVC, and provides practical code examples demonstrating how to build a reactive web application using Spring Boot, Reactor's Mono and Flux, and functional routing.
To overcome Go’s per‑connection goroutine memory and GC limits at massive scale, the article designs a three‑layer Reactor‑based network library that uses epoll/kqueue, lock‑protected file descriptors, zero‑copy buffers, and load‑balanced sub‑reactors, enabling stable operation with up to a million concurrent connections.
This article provides a comprehensive, code‑driven walkthrough of Netty's internal networking architecture, covering NioEventLoopGroup, selectors, channels, pipelines, bootstrap configuration, binding mechanics, and how new connections and user requests are processed in a Java server environment.
This article introduces Netty, explains Java's BIO/NIO/AIO models, compares reactor threading architectures, details Netty's internal thread and handler pipeline design, and provides a complete example of building a high‑performance HTTP server with Netty.
The article dissects netpoll, a Go‑based high‑performance network framework that uses a Multi‑Reactor model with a main and sub‑reactors, detailing its server EventLoop, poll manager load‑balancing across epoll/kqueue, connection buffering and request handling, and the client’s non‑blocking dialing process.
This article explains the limitations of traditional blocking I/O, introduces Java NIO with selectors, compares the two models using a kindergarten analogy, critiques raw JDK NIO, and demonstrates how Netty simplifies and optimizes network development with concise server and client code examples while promoting a comprehensive Netty learning book.
This article explains the fundamentals of Reactor's reactive programming model—including Mono and Flux types, map and flatMap operators, asynchronous execution, scheduler choices, and error handling—while providing practical code examples to help developers efficiently use Spring WebFlux.
The article explains how Spring WebFlux, built on the Reactor project, offers a non‑blocking, reactive alternative to traditional Spring Web MVC, detailing its relationship with servlet containers, the advantages of Reactive Streams, and considerations for adopting it in Java backend development.
This tutorial provides a detailed introduction to Netty, covering its architecture, core concepts such as buffers, channels, selectors, reactor thread models, zero‑copy techniques, and includes practical TCP server/client code examples, helping readers understand and apply Netty for high‑performance Java network programming.
This article explains Netty as an asynchronous event‑driven network framework, compares synchronous and asynchronous processing, describes event‑driven programming, details the differences among BIO, NIO and AIO I/O models, and outlines Netty's core components and architecture.
This article walks through the progression of Java server‑side I/O—from classic blocking BIO, through multithreaded and thread‑pool BIO variants, to non‑blocking NIO and Reactor‑based scalable designs—explaining core concepts, code examples, and performance trade‑offs.
The article explains IO models—from blocking IO’s limitations to non‑blocking and multiplexing techniques like select, poll, and epoll—then shows how libevent encapsulates these mechanisms to provide a Reactor‑style event‑driven framework, illustrated with a simple echo server implementation.
This article explains what Netty is, reviews traditional HTTP server processing, introduces Java NIO and its non‑blocking event model, compares BIO and NIO, describes Netty's reactor thread architectures, discusses TCP sticky/half‑packet problems and their solutions, and details Netty's zero‑copy techniques for high‑performance networking.
This article explains the main components of Cloud Foundry, the role of the NATS messaging system, and compares the Reactor and Proactor patterns for synchronous and asynchronous I/O, providing detailed step‑by‑step workflows for read and write operations.
This article explains the fundamental concepts of I/O models—including synchronous vs. asynchronous, blocking vs. non‑blocking, the five classic I/O models, and the Reactor and Proactor design patterns—using clear definitions, examples, and Java code snippets to illustrate each approach.