The article reviews the GitHub “public-apis” repository, which lists more than 1,700 free APIs across 51 categories, explains its classification, entry details, contribution rules, companion API endpoints, and practical use cases such as demos, prototyping, and building internal tools.
The article examines how backend performance tuning is evolving from manual, experience‑driven cycles to data‑driven observability, closed‑loop AIOps, serverless/Wasm architectures, and energy‑aware optimization, outlining concrete examples, tools, and forecasts shaping the field through 2026.
The article explains how a fast SQL statement can occupy a database connection for hundreds of milliseconds because Spring’s @Transactional starts the transaction and acquires the connection long before the first JDBC statement, and shows how the new Spring Boot 4.1 `connection‑fetch: lazy` setting postpones the acquisition to solve the problem.
This article walks through building a production‑grade Netty TCP server, covering protocol design, reactor threading, back‑pressure handling, session management, authentication, heartbeats, scaling to hundreds of thousands of connections, cloud‑native deployment, graceful shutdown, observability, reliability, and security considerations.
Go 1.25 introduces a second version of the json package with new capabilities, API fixes, and performance improvements, but also many breaking changes; this article walks through the core differences, migration pitfalls, new streaming interfaces, option controls, tag extensions, custom codecs, default behavior shifts, and performance considerations.
Spring Boot 4.1 adds the functional interface InetAddressFilter, enabling HTTP clients to block or allow requests based on IP ranges; the article shows how to configure the filter as a bean, apply it to RestClient/WebClient, and verify that internal‑network SSRF attempts are prevented.
The article surveys ten practical performance‑optimization tactics—from classic indexing, compression, and caching to prefetching, peak‑shaving, batch processing, and advanced methods such as resource squeezing, horizontal scaling, sharding, and lock‑free designs—explaining their trade‑offs, concrete examples, and when to apply each in real‑world systems.
Go 1.27 introduces generic methods, struct‑literal key selectors, expanded function‑type inference, a complete rewrite of the JSON package with encoding/json/v2, native post‑quantum signature support, a GA goroutine‑leak detector, 30 % faster small‑object allocation, and numerous toolchain and ecosystem refinements that together reshape the language, standard library, runtime, and developer experience.
The article explains how Spring Boot 4.1’s new spring.datasource.connection-fetch setting can delay acquiring a physical database connection until a SQL statement is executed, reducing unnecessary connection usage in high‑traffic scenarios and improving overall system concurrency.
This article walks through the end‑to‑end design of a production‑grade Nginx‑based WebSocket gateway that can handle a million concurrent connections, covering the five essential requirements, detailed Nginx settings, backend gateway responsibilities, load‑balancing strategies, observability, common failure patterns, and step‑by‑step Go code examples.
In high‑throughput wallet systems, reconciliation—covering internal balance validation, channel‑level matching, and controlled auto‑repair—acts as the final safeguard against fund discrepancies caused by lost callbacks, out‑of‑order events, duplicate entries, or concurrency conflicts, ensuring financial safety even with billions of daily transactions.
The article explains how Spring's @Autowired and Java's @Resource annotations differ in their injection strategies, origins, matching priorities, and typical pitfalls, using a payment‑service example to illustrate each rule and provide practical guidance for avoiding common errors.
The article explains RocketMQ's two‑layer locking mechanism that guarantees ordered consumption by holding a queue‑level lock inside a while loop, clarifies why autoCommit only affects offset reporting, and shows how the client correctly processes multiple messages in a single thread.
The article explains how RocketMQ’s transactional message mechanism guarantees consistency between order creation and inventory deduction by using half‑messages, a local transaction callback, a second‑phase confirmation, and broker‑side timeout checks, while highlighting common pitfalls and best‑practice recommendations.
The article examines why the early hype around Java virtual threads has faded, detailing technical pitfalls such as pinning and ThreadLocal memory bloat, incomplete ecosystem support, and misuse in CPU‑bound workloads, while also presenting benchmark data that shows they still excel in I/O‑heavy scenarios.
The article explains why gRPC is gaining popularity by comparing its performance, streaming capabilities, and cross‑language contract advantages over traditional REST + JSON, and provides a step‑by‑step guide to building a complete gRPC service with Spring Boot 4.1.
The article walks through a real incident where a scheduled batch job contained an infinite while‑true loop, causing all 500 HikariCP connections to be held, slowing the application dramatically; it details the investigation steps, root‑cause analysis, and both emergency and long‑term fixes, plus a checklist to avoid similar bugs.
The article walks through why embedding a wallet in the order service leads to boundary violations and failures under load, and presents a step‑by‑step evolution from an order‑centric wallet to a dedicated, event‑driven accounting center that ensures consistency, auditability, and high‑throughput scalability.
This article compares embedded Tomcat (bundled inside a Spring Boot executable JAR) with standalone Tomcat (installed separately), covering installation, packaging, resource usage, startup speed, management, version flexibility, feature set, pros and cons, and guidance on selecting the appropriate deployment model.
The article explains the background of long Java restart times, defines hot swap and hot deployment, details their implementation mechanisms, compares their granularity, speed, limitations, and impact, lists common tools, and highlights frequent misconceptions and pitfalls for developers.
