1 views collected around this technical thread.
This tutorial explains how to build scalable, maintainable FastAPI APIs by modularizing routers, implementing path‑based version control, centralizing dependency injection, applying role‑based access control, using custom middleware, and nesting routers for complex applications.
This article explains the concept of MySQL optimistic locking, its underlying version‑or‑timestamp mechanism, and provides step‑by‑step SQL examples for adding a version column, reading data, and safely updating records while handling concurrent modifications.
This guide presents comprehensive Laravel API development best practices for 2025, covering authentication with Sanctum and Passport, resource formatting, versioning, rate limiting, error handling, caching, and logging, offering code examples and practical advice to build secure, scalable, high‑performance APIs.
This article provides a thorough guide on API (interface) fundamentals, design principles, optimization techniques, security measures, and maintenance practices, offering practical examples and code snippets for building robust, high‑performance modern backend services.
This article explains how to achieve idempotent order creation and updates by using unique request identifiers, database primary‑key constraints, Redis flags, and a version‑column strategy to prevent duplicate submissions and resolve the ABA anomaly in distributed systems.
This article explains how to detect frontend deployment changes and prompt users to refresh by generating a git‑hash JSON file with git‑revision‑webpack‑plugin, creating Vue mixins for version checking, and comparing hashed filenames in the built index.html, covering three practical solutions with their pros and cons.
This article explains how to create a custom insert annotation and an annotation processor in Java to automatically inject the jar version into component constants at compile time, enabling Prometheus monitoring without manual version updates.
The article explains how to achieve idempotent order creation and updates by using unique order IDs, database primary key constraints, Redis flags, and a version column to prevent duplicate inserts and solve the ABA problem in distributed backend systems.
This article examines typical high‑concurrency scenarios such as payment processing, online ordering, and cross‑bank transfers, introduces the Compare‑and‑Swap (CAS) approach to ensure strong consistency, explains the ABA problem it can cause, and presents application‑level and data‑layer strategies—including versioning and SQL examples—to mitigate it.
This article explains how to achieve idempotent order creation and updates by using unique order IDs, database primary key constraints, Redis flags, and version columns to prevent duplicate submissions and resolve the ABA problem, ensuring consistent data across distributed services.
This article explains a systematic firmware version numbering scheme—including project name, major/minor versions, build ID, and release type—provides a detailed table of the format, shows a concrete example, and offers best‑practice tips for linking each image to its corresponding Git commit.
The article explains how to achieve idempotent order creation and updates by using database transactions, unique order identifiers, Redis flags, and version columns to prevent duplicate inserts, handle retry scenarios, and solve the ABA problem in distributed backend systems.
Semantic Versioning (SemVer) is a structured software versioning scheme that uses a three-part major.minor.patch format to clearly convey the impact of changes, guiding developers through initial development, stable releases, subsequent updates, and special pre‑release or build metadata versions.
Learn how to implement multi-version REST APIs in SpringBoot 2.7.16 using a single custom annotation, custom RequestCondition, and HandlerMapping, enabling seamless version control, client compatibility, and flexible business scenarios with clear code examples and testing screenshots.
This article explains the concept of optimistic locking in concurrent programming, details four common implementation approaches—version number, timestamp, CAS, and serial number—their underlying mechanisms, and outlines typical scenarios where optimistic locks improve data consistency and performance.
This article provides an in‑depth overview of Go Modules, covering its history, core concepts such as modules, packages, versioning, environment variables, the Minimal Version Selection algorithm, and practical commands for initializing projects, adding, upgrading, and downgrading dependencies, all illustrated with real code examples.
This article explains why and how to build a reusable business component library for frontend teams, compares single‑package and multi‑package architectures, details the build process using webpack and Rollup, describes version‑control strategies, outlines a SOP for component development, and provides practical code examples.
This article describes a comprehensive solution for notifying B2B web users about outdated frontend versions, covering the problem background, version number generation, trigger conditions, micro‑frontend adaptation, detailed plugin and React component code, integration steps for main and sub‑applications, debugging guidance, and measured user impact.
Oracle announces a new MySQL version model that separates Innovation releases, which deliver new features and frequent updates, from Long‑Term Support (LTS) releases that provide stable, minimal‑change versions with extended support, outlining upgrade paths, deprecation policies, and detailed release schedules.
Oracle announces a new MySQL version model that separates Innovation releases, which deliver new features and frequent updates, from Long‑Term Support (LTS) releases that provide stable, minimal‑change versions with extended support, outlining transition paths, upgrade‑downgrade strategies, and product portfolio impacts.