How Node.js Web Frameworks Evolved: From Express to Midway’s Front‑End‑Friendly Design

Node.js & Web Framework Overview

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

Web Framework Functions

Modern web development relies on frameworks that provide RESTful APIs, database CRUD, page rendering, authentication, and other essential capabilities, while also imposing conventions that guide scalable application architecture.

Node.js Framework Evolution Stages

Node.js framework development can be divided into three phases: the startup phase, the enterprise architecture phase, and the front‑end‑oriented phase.

Startup Phase – Lightweight

2009 saw the emergence of Node.js, followed by Express in 2010 and Koa in 2013. Early adopters experimented with Node.js for feasibility, favoring minimalistic, easy‑to‑learn frameworks.

Express is easy to integrate with Nest and Webpack, while Koa integrates smoothly with Egg and Midway. Their strengths are simplicity, rich ecosystems, and proven stability; their weaknesses include lack of standards, limited best‑practice guidance, and aging codebases.

Enterprise Phase – Architecture‑Focused

From 2014 to 2017 Node.js scaled to large‑scale production, giving rise to professional engineers and enterprise‑grade frameworks such as Nest, Egg, and Midway, often built atop Express or Koa.

These frameworks offer comprehensive features, clear conventions, and active community support, but they also bring higher learning curves and reduced extensibility.

Front‑End‑Oriented Phase

Since 2016, with Node 4.0 and a surge of front‑end engineers, frameworks like Next.js and Nuxt.js emerged, emphasizing simplicity, full‑stack capabilities, and Serverless deployment. Their advantages are ease of learning for front‑end developers and rapid iteration; drawbacks include weaker back‑end functionality and limited custom extensibility.

According to the State of JS 2020 survey, Next.js topped the satisfaction chart, while Express.js remained widely used.

Midway – A Front‑End‑Friendly Framework Journey

Midway, launched in 2014 and open‑sourced in 2018, is an enterprise‑grade framework built with TypeScript, IoC, and Egg ecosystem reuse.

Challenges Identified

Low server utilization: over 1,600 Node.js services averaged CPU usage below 10%.

High DevOps cost: Docker, rate‑limiting, logging, and cross‑language concerns increased operational overhead.

Fragmented user base: front‑end engineers desire simple, quick APIs, while back‑end engineers need robust, maintainable architectures.

Progressive Design Solutions

Midway adopts a layered, progressive design: core, coding paradigm, ecosystem, scenario‑specific extensions, and modern web features. Hooks are introduced to treat functions as interfaces, provide automatic request context, and enable “zero‑API” calls where front‑end code directly imports TypeScript functions without generating separate API contracts.

Modular, Lego‑Like Evolution

Features are offered as composable blocks—project type, development style, plugins, triggers, deployment platform—allowing developers to assemble solutions ranging from front‑end‑centric full‑stack apps (hooks, config, HTTP, FaaS) to back‑end‑heavy services (IoC, decorators, ORM, Swagger, gRPC).

Key Takeaways

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

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

Full‑stack, front‑end‑oriented frameworks drive simplicity, lightweight design, and better developer experience.