0 views collected around this technical thread.
This article explains the importance of browsers for both front‑end and back‑end developers, outlines the historical evolution from early single‑process designs to modern multi‑process architectures, and details core components, rendering engines, and market share, providing a comprehensive technical overview.
The article explores the motivations behind mini programs, micro‑frontends, and module loading, comparing their technical advantages, business implications, and ecosystem challenges while questioning whether these solutions truly address core problems or merely serve as market‑driven silver bullets.
This article explains the concepts and differences of URI, URL, and URN, describes their hierarchical relationship, outlines URL components, discusses Data URI syntax, presents best‑practice guidelines for stable and user‑friendly URL design, and provides real‑world examples such as Flickr API URL patterns.
This article explains the differences between URI, URL and URN, outlines best‑practice principles for designing stable, readable and user‑friendly URLs, discusses technical details such as Data URIs, mapping, redirects, and provides concrete examples including Flickr API URL patterns.
Effective URL design, covering the distinctions and relationships among URI, URL, and URN, best practices for stability, readability, and longevity, as well as technical considerations such as Data URIs, hash fragments, redirects, and real‑world examples like Flickr, provides essential guidance for web architects and developers.
This article explains the concepts, differences, and hierarchical relationships of URI, URL, and URN, discusses common pitfalls and design guidelines for stable and user‑friendly web addresses, and provides practical examples such as Data URI syntax, Flickr API URL patterns, and HTTP redirection strategies.
Front‑end development has progressed from early back‑end‑only sites to a distinct discipline covering HTML, CSS, and JavaScript, embracing SPA techniques, micro‑frontend architectures, and full‑stack capabilities via Node.js and BFF layers, requiring engineers to grasp both client presentation and server‑side concepts for collaborative, modular, reusable web applications.
This article explains the motivations for separating frontend and backend, outlines the evolution from MVC to SPA architectures, details responsibilities, development workflows, and provides a comprehensive API specification including request/response formats, special data handling, and future frontend trends.
This article explains the complete web request lifecycle—including DNS lookup, caching mechanisms, HTTP/HTTPS communication, TCP/UDP transport, gateway routing, backend service models, virtualization, Docker containerization, and Kubernetes orchestration—providing engineers with a solid foundation for diagnosing and optimizing modern web applications.
This article explains the necessity of Single Sign-On (SSO) in multi‑system environments, traces its origins from monolithic web applications to distributed clusters, and describes common implementation approaches for same‑domain and cross‑domain scenarios, including the use of a central authentication center such as CAS.
This article introduces the Jamstack architecture, compares it with traditional web stacks, and details how Douyin's e‑commerce 818 main‑hall performance optimization project applied Jamstack principles, CDN caching, API prefetching, and client‑side techniques to achieve faster, more scalable page delivery.
The article outlines the defining traits of large-scale websites—high concurrency, massive data, 24/7 availability, security, and rapid iteration—and discusses major technical challenges such as scaling, caching, clustering, database read/write separation, CDN acceleration, distributed storage, and service decomposition.
This article walks through the step‑by‑step architectural evolution of a Java Web e‑commerce platform, covering initial single‑machine deployment, separation of application and database servers, clustering, load‑balancing algorithms, session handling, read/write splitting, search integration, caching, database sharding, microservice decomposition, SOA governance, and the introduction of message middleware.
Static and dynamic resource separation, commonly known as static‑dynamic separation, involves deploying static files (HTML, JavaScript, CSS, images) on a web server like Nginx while forwarding dynamic requests to a backend application server via reverse proxy, thereby improving static asset delivery speed and enabling parallel front‑end and back‑end development.
This article walks through the step‑by‑step evolution of a Java web e‑commerce platform, covering initial single‑machine deployment, server‑database separation, application clustering, load‑balancing techniques, read‑write splitting, caching, database sharding, service‑oriented architecture, and the introduction of messaging middleware to achieve a highly scalable and maintainable system.
The article examines the reasons for combining PHP and Java in web architecture, highlighting PHP’s rapid front‑end development and flexibility, Java’s performance and stability for back‑end services, and discusses the trade‑offs, challenges, and practical experiences of dual‑language systems.
Tips is an open‑source static‑text management platform that lets front‑end developers and non‑technical staff instantly edit UI prompts and page content through an embedded JavaScript SDK and web console, supporting internationalization, permission‑based toggles, and immediate or publish‑controlled updates, eliminating full deployment cycles.
The article explains how traditional Java web projects that bundle JSP, static assets, and business logic into a single WAR cause performance and scalability issues, and advocates separating front‑end static resources from back‑end services to achieve true decoupling, better fault tolerance, and easier horizontal scaling.
This article explains the role of a middle tier in web systems, describes middleware concepts, outlines the advantages of using Node.js as a middle layer, and provides a step‑by‑step Koa‑based implementation with code examples and deployment considerations.
This article explains what OpenResty is, details its underlying Nginx‑Lua architecture—including Lua coroutines, cosocket, and multi‑stage processing—compares its performance with other web platforms, and describes its practical deployment and multi‑level caching strategy in JD.com's high‑traffic Jshop sale system.