This article details how Fliggy's front‑end team tackled the performance challenges of the Double‑11 shopping festival by migrating to Rax 1.0 on Web, employing pre‑render, Serverless SSR, Snapshot caching, SPA techniques, and comprehensive monitoring, ultimately achieving a 25% reduction in first‑screen load time.
The article details how Vivo’s official mall migrated from a heavy SPA to a Nuxt‑based server‑side rendering solution, employing LRU page caching, component and API caches, concurrent requests, selective client‑only rendering, robust degradation tactics, automated CI/CD deployment, and monitoring, which together boosted QPS from 125 to 6 000—a roughly fifty‑fold performance gain and markedly better user experience.
San, Baidu’s lightweight MVVM component framework launched in 2016, combines Vue‑inspired templates, high performance, tiny bundles, and IE6+ compatibility, offering server‑side rendering and a robust ecosystem, and has delivered measurable efficiency and speed gains across Baidu’s flagship web products.
This article explains what responsive design is, outlines its advantages such as resource savings and SEO benefits, discusses the difficulties encountered with media queries in Ctrip's train‑ticket project, and presents concrete class‑based and server‑side solutions with code examples to improve maintainability and performance.
In 2020 Alibaba upgraded its Double 11 e‑commerce venue by introducing a low‑risk data‑driven Server‑Side Rendering (SSR) solution that lifted the page‑open rate to 82.6% and increased UV click‑through by up to 5%, while detailing the architectural changes, performance metrics, implementation challenges, and measurable business impact.
This article explains how the 2020 Double‑11 e‑commerce event page adopted server‑side rendering to dramatically improve first‑paint metrics, reduce page‑load time, boost user engagement, and overcome the limitations of the existing client‑side rendering architecture through a low‑risk, data‑driven SSR solution.
Facing slow page loads on weak mobile networks, Alibaba’s Feizhu marketing team adopted a Serverless Faas SSR solution combined with async rendering, reducing first‑screen time to under one second, improving offline capabilities, and addressing challenges like image flicker, titlebar support, and scaling performance.
The article introduces Offline Prerender (OPR), explains why traditional SSR and SPA first‑screen optimizations have limitations, details the OPR workflow—including scheduled Puppeteer rendering, HTML capture, data injection, diffing, CDN upload, and delayed mounting—and shares practical enhancements such as CSS tree‑shaking, async script loading, and downgrade strategies, demonstrating significant speed gains.
Vivo Mall transformed its Java‑centric frontend into a layered Vue‑Node architecture, separating frontend and backend, unifying multiple platforms with BFF and SSR, building a shared UI library, adopting extreme modularization, and enforcing coding standards and quality tools to double development efficiency and improve scalability.
This article explains why and how to enable CDN caching for server‑side rendered pages, outlines the conditions for its use, offers optimization tips, and provides step‑by‑step Koa middleware code to control cache behavior and avoid common pitfalls.
The talk reviews Serverless origins, defines its cloud‑native architecture that lets developers focus on business logic, highlights benefits like pay‑per‑use scaling, demonstrates rapid Next.js SSR deployment via the Serverless Framework with built‑in monitoring, and outlines a top‑down development and operations workflow.
This article explains how leveraging edge computing, CDN‑based SSR caching, and TESI tags can dramatically improve first‑screen performance, reduce server pressure, and enable efficient static rendering for massive, mostly static content while maintaining up‑to‑date data and robust fallback mechanisms.
This article explores the limitations of traditional front‑end performance techniques for first‑page loads and introduces a new Edge Stream Rendering (ESR) approach that leverages CDN edge computing to stream static and dynamic content sequentially, reducing TTFB, white‑screen time, and core content display latency across various network conditions.
This article explores how the shift from traditional Backend‑For‑Frontend (BFF) to Serverless‑For‑Frontend (SFF) and the evolution of JAMstack into JAMS, combined with FAB bundles and serverless‑side rendering, can dramatically improve developer experience, performance, and scalability for modern web applications.
This technical guide explains how to build a Vue SSR service using Koa, outlines the project benefits and trade‑offs, details the directory structure, server and client entry files, webpack configurations, and describes a Docker‑based CI/CD pipeline with Kubernetes deployment for scalable production environments.
This article walks through the benefits, trade‑offs, and step‑by‑step implementation of Vue server‑side rendering using Koa, then shows how to containerize the service with Docker and automate deployment with Kubernetes, covering code, configuration, and common pitfalls.
This article explains how Rax's Server‑Side Rendering delivers six‑times the performance of React, outlines the challenges of SSR development, and shows how Serverless integration can simplify deployment while maintaining superior rendering speed, especially on weak networks.
This article explains how Alibaba's open‑source Rax framework improves front‑end performance through lightweight bundles, adaptive hydration, snapshot rendering, server‑side and native side rendering, and personalized rendering strategies, aiming to keep first‑screen interaction under three seconds even during massive traffic spikes.
This article examines the rapid rise of Serverless in 2019, analyzes the specific front‑end challenges it creates, explores framework and rendering adaptations such as Egg.js, Next.js and Umi SSR, and proposes architectural upgrades and future directions for more efficient, empowered front‑end development.
This article describes how the M page’s user‑perceived performance was dramatically improved by applying techniques such as SSR, skeleton screens, image compression, and a video‑frame analysis testing method that delivers millisecond‑level response‑time measurements, enabling sub‑second load times and eliminating white‑screen delays.
This article presents a comprehensive guide to improving Vue application performance, covering code‑level tricks such as proper use of v‑if/v‑show, computed vs watch, key handling, lazy loading, and SSR, alongside webpack configuration tweaks, image compression, source‑map tuning, and fundamental web optimizations like gzip and CDN usage.
The article explains how serverless cloud functions can replace traditional SSR servers by running isomorphic React/Vue rendering within a FaaS environment, detailing the architecture, packaging, debugging, NGW gateway integration, performance bottlenecks like cold starts, and optimization strategies that cut deployment and operation effort by over 80%.
This article shares the evolution and practical application of Node.js at WeDoctor, detailing its rapid adoption for internal efficiency tools, Vue server‑side rendering, API services, full‑stack frameworks, and ecosystem enhancements such as tracing and performance monitoring, illustrating how front‑end engineers can leverage Node.js to boost productivity and reliability.
Rax 1.0 introduces a major version upgrade with Hooks, Alipay mini‑program support, a dramatically reduced bundle size, improved web experience and server‑side rendering, while providing richer documentation, plugin architecture, and a new website to boost development efficiency.
This article examines the evolution from backend template engines to SPA, highlights SPA's SEO and first‑paint drawbacks, and presents a detailed Vue server‑side rendering implementation with optimization techniques, degradation strategies, and performance results showing over 300% faster first‑screen rendering.
This article walks through the concepts, architecture, and step‑by‑step implementation of a React + Redux isomorphic application that renders on the server with Koa, bundles with Webpack, and hydrates on the client, while highlighting performance benefits and common pitfalls.
The May 25 WeDoctor Frontend Tech Salon, themed “Boundless,” gathered over 30 external companies and 100 internal participants to explore server‑side rendering, desktop and cross‑platform front‑end development through six technical talks covering Vue SSR, Node.js micro‑services, exception monitoring, NW.js, WebView integration, and Weex implementation.
The article describes how NetEase migrated its Open Course PC site from a legacy CMS to a high‑performance Node.js SSR architecture using Egg.js with TypeScript and Nuxt.js, detailing integration, caching, logging, error monitoring, middleware ordering, and achieving 338.6 TPS on a single 4‑core server.
Developers must decide where rendering occurs—server-side, client-side, static generation, or rehydration—by understanding key terms, performance metrics like TTFB, FP, FCP, and TTI, and weighing trade‑offs such as speed, resource usage, SEO impact, and complexity across modern frameworks.
This article details the adoption of NodeJS and the Egg framework for front‑end/back‑end separation, covering SSR considerations, directory planning, scheduled tasks, error handling, service design, custom logging, Elasticsearch integration, and Docker deployment, offering practical insights and best‑practice recommendations for backend development.
This guide walks you through the fundamentals of Nuxt.js server‑side rendering, covering installation, project scaffolding, routing, asset handling, layouts, middleware, plugins, and configuration to build fast, SEO‑friendly Vue applications.
Uniqy replaces iQIYI’s legacy qiyiV2 with a Vue 2‑based framework that combines server‑side rendering, PJAX navigation, decorator‑style class components, and lazy‑loaded modules, delivering faster first‑screen loads, better maintainability, SEO friendliness, and graceful fallback for low‑end browsers.
The article explains how Meituan’s build‑time pre‑rendering, using a TypeScript decorator and PhantomJS to generate static HTML for selected routes, eliminates the first‑frame white screen, employs request hijacking for CDN assets, and achieves a 75% reduction in first‑contentful‑paint time, dramatically boosting mobile user experience.
This article details a front‑end engineer's experience building a hotel mini‑program with the DACE framework—covering its React‑based SSR architecture, module organization, data fetching strategies, custom components, webpack code‑splitting, and the challenges and insights gained during development, integration, and deployment.
This article explains how React 16 rewrote its server‑side rendering layer to support four rendering modes—including string and streaming approaches—by introducing the ReactPartialRenderer and ReactMarkupReadableStream classes, and details the process of converting virtual DOM trees into HTML strings.
This article chronicles Bilibili’s front‑end evolution in 2017, detailing the shift from a backend‑centric MVC model to front‑back separation, the adoption of Node middle‑layers, Vue and React SSR, Docker deployment, caching strategies, and subsequent refactoring to improve performance and scalability.
This article chronicles Bilibili’s 2017 front‑end transformation, detailing the shift from a backend‑centric MVC workflow to a decoupled architecture with Node middleware, Vue SSR, Docker deployment, configuration management, caching strategies, and performance testing, illustrating lessons learned and future directions.
The article introduces the Hawaii framework—a Node.js based server‑side rendering solution used by WeChat HandQ—detailing its background, core RDS request description files, component architecture, development workflow, comparison with React/Vue and GraphQL, and its deployment and monitoring strategies.
The article outlines Meituan‑Dianping’s approach to front‑end service availability for its checkout system, defining availability across code, static resources, and network links, measuring failure duration, identifying typical bugs, and implementing a three‑stage assurance strategy using people processes, engineering tools, lightweight technology choices, and concrete practices such as TypeScript adoption, automated testing, health‑checks, DNS protection, and post‑incident monitoring.
The article introduces the concept of isomorphic JavaScript, explains its types and hierarchical levels, outlines its practical benefits such as SEO and faster first‑load experience, and details the IMVC framework and the create‑app library that enable seamless server‑client code sharing with a clear controller‑model‑view separation.
This article explains how to implement server‑side rendering (SSR) for Vue.js applications, covering the underlying concepts, required code setup, Vuex state handling, webpack configuration, and deployment steps to improve SEO for single‑page applications.
This article introduces a Webpack2‑based React‑Redux boilerplate, detailing its architecture, core features, configuration options, development workflow, server‑side rendering support, and best‑practice recommendations, while providing code examples and guidance for both beginners and experienced frontend developers.
This article details the challenges of evolving a large legacy frontend codebase, the transition from jQuery and fis3 to React with TypeScript, the integration of webpack-like features, server‑side rendering techniques, and the use of yog2, Fit, and related tooling to streamline modern web development.
LinkedIn’s engineering team completely rebuilt its homepage using Play and dust.js, achieving faster load times, daily releases, and extensive automation through server‑side rendering, BigPipe streaming, lazy image loading, and reduced redirects, while continuing to explore Scala, Java 8, and client‑side MVC frameworks.
