Node.js Web Framework Evolution: From Express to Midway and Front‑End‑Friendly Design

Node.js & Web Framework Overview

Node.js is a runtime built on the Chrome V8 engine, used for CLI tools, data processing, RESTful APIs, and page rendering, dramatically expanding JavaScript beyond the browser.

Web Framework Functions

Modern web frameworks provide RESTful APIs, database CRUD, page rendering, authentication, and other essential capabilities, while also imposing conventions that drive continuous innovation.

Node.js Framework Development Stages

Startup phase (2009‑2013): Lightweight frameworks like Express (2010) and Koa (2013) emerged, emphasizing simplicity and minimalism. Their advantages include easy learning curves and strong ecosystems, but they lack standardized best practices and can hinder large‑scale collaboration.

Enterprise phase (2014‑2017): As Node.js scaled, enterprise‑grade frameworks such as Nest, Egg, and Midway appeared, offering comprehensive features, clear conventions, and robust community support, at the cost of higher onboarding complexity.

Front‑end‑oriented phase (post‑2016): With the rise of front‑end engineers, frameworks like Next.js and Nuxt.js focus on full‑stack simplicity, serverless deployment, and tight integration with front‑end tooling, though they may provide weaker back‑end capabilities.

2020 State of JS survey shows Next.js topping satisfaction rankings while Express remains widely used.

Midway – Evolution of a Front‑End‑Friendly Framework

Midway, initiated in 2014 and open‑sourced in 2018, is an enterprise‑grade framework built with TypeScript, IoC, and Egg ecosystem reuse. It addresses internal Alibaba challenges such as low server CPU utilization (<10%) and high DevOps costs.

Front‑end teams demand rapid composition of services, tighter front‑back integration, and cloud‑native efficiency.

Alibaba’s front‑end committee identified four technical directions for 2019‑2020: service construction, Serverless, intelligence, and IDE support.

Challenges and Progressive Design

Key challenges include divergent user groups (front‑end vs. back‑end engineers), differing scenario requirements (simple CRUD vs. complex enterprise needs), and a paradigm shift from class components to function‑plus‑hooks.

Midway’s solution is a progressive, modular design:

Hooks: Functions act as interfaces, providing automatic request context via useContext and enabling zero‑API calls through direct TypeScript imports.

Full‑stack design: Unified source directory for server, API, and front‑end assets.

Modular building blocks: Developers assemble projects by selecting components (e.g., function, config, HTTP, FaaS) like LEGO bricks, supporting both front‑end‑centric and back‑end‑centric applications.

Adoption and Impact

Midway Hooks launched in April 2020, now powering over 2,500 applications within Alibaba and becoming the mainstream development model for front‑end engineers.

Final Takeaways

Node.js web framework evolution mirrors front‑end industry trends.

Front‑end scenarios outnumber pure back‑end use cases.

Progressive, front‑end‑friendly full‑stack frameworks drive simplicity, lightweight development, and better developer experience.

Future – Standards & Planning

Type‑safe end‑to‑end development is emerging, with proposals like Prisma for ORM generation and community efforts toward JS Module Blocks and JS Module Fragments, aiming to unify server, SSR, and client code in a single file. Alibaba’s front‑end committee is contributing to TC39 proposals to advance these standards.