Tagged articles
separation
19 articles · Page 1 of 1
This article traces the historical evolution of web application architecture—from tightly coupled JSP/Servlet models through semi‑separated Ajax‑driven approaches to fully separated SPA and Node.js‑mediated full‑stack designs—highlighting the motivations, drawbacks, and benefits of each stage for modern front‑end development.
frontendnodejsseparation
0 likes · 14 min read

The article explains why front‑back end separation is needed, outlines common collaboration patterns, presents a staged migration from MVC to SPA, and provides detailed API request/response standards, interface versioning, and practical steps for implementing clean separation in modern web projects.
APIBackendarchitecture
0 likes · 12 min read

This article explains why front‑back end separation is needed, describes the evolution from MVC to SPA, outlines the principles of responsibility and concern separation, and provides a detailed API specification—including request/response formats, pagination, and special field handling—to improve collaboration and reduce integration effort.
Backendarchitecturefrontend
0 likes · 14 min read

The article explains how front‑end/back‑end separation restructures development by letting front‑end teams handle UI and interaction while back‑end teams expose data via RESTful APIs, improving modularity, parallel work, deployment flexibility, and overall system scalability.
APIarchitecturedeployment
0 likes · 6 min read

This article explains why and how to separate frontend and backend development, outlines the evolution from MVC to SPA architectures, and provides detailed API design standards—including request/response formats, pagination, and special data types—to improve collaboration, reduce integration effort, and prepare for future front‑end‑centric trends.
APISPAseparation
0 likes · 12 min read

The article explains why front‑back end separation is needed, describes the evolution from MVC to SPA, outlines responsibility separation, development workflow, and presents a detailed API specification including request/response formats, pagination, and special data handling rules.
APIBackendMVC
0 likes · 10 min read

This article explains why front‑end and back‑end separation is needed, describes the evolution from MVC to SPA, outlines responsibilities, development workflow, and provides a detailed version‑1.0.0 API contract with request/response formats, special field rules, and future front‑end trends.
APIBackendarchitecture
0 likes · 13 min read

This article explains the evolution from MVC to SPA, highlights the pain points of tightly coupled front‑end and back‑end development, and provides concrete responsibility separation, development processes, and a detailed API specification to enable efficient, loosely‑coupled collaboration in modern web projects.
API DesignBackendSPA
0 likes · 14 min read

This article explains why front‑end and back‑end should be separated, describes the evolution from MVC to SPA, outlines responsibilities, development workflow, and provides a detailed version‑1.0.0 API contract including request/response formats, pagination, special data types, and mock‑server usage.
AJAXSPAfrontend
0 likes · 12 min read

The article explains common development models, detailing the steps from requirement gathering to delivery, compares half‑separation and full separation of frontend and backend, outlines their advantages and disadvantages, and reflects on architectural responsibilities in line with Conway's Law.
BFFarchitecturedevelopment process
0 likes · 3 min read

The article traces the historical evolution from tightly coupled JSP/Servlet MVC architectures through semi‑separated Ajax/SPA patterns to fully decoupled front‑end/back‑end separation, highlighting the advantages of introducing Node.js as a middle‑layer to improve adaptability, performance, and development efficiency.
Webfrontendnodejs
0 likes · 13 min read

This article explains why front‑end/back‑end separation is needed, describes the evolution from MVC to SPA, and provides detailed API design rules, request/response formats, and implementation steps to achieve a clear, maintainable, and efficient development workflow.
APIBackendSPA
0 likes · 12 min read

From legacy JSP‑based MVC to semi‑separated Ajax‑driven pages and finally fully separated front‑end architectures using Node.js, this article examines each stage’s structure, advantages, and drawbacks, arguing that small‑to‑mid‑size companies must weigh resource constraints, performance, and maintenance before fully embracing front‑end separation.
AJAXMVCNode.js
0 likes · 12 min read


ITPUBJun 16, 2018 · Frontend Development
The article walks through the evolution of front‑end development from traditional JSP/Servlet MVC through semi‑separated Ajax‑driven pages to fully separated front‑back architectures, highlighting each stage’s structure, advantages, drawbacks, and the practical considerations that make full separation risky for small‑to‑medium projects.
AJAXMVCNode.js
0 likes · 12 min read

The article examines the evolution of web development models, explains why naive front‑end/back‑end separation often leads to problems, and offers practical guidelines—including team roles, RESTful API design, collaboration patterns, and deployment strategies—to implement a successful separation architecture.
BackendRESTfularchitecture
0 likes · 8 min read

This article explains why front‑end/back‑end separation is increasingly popular, outlines its benefits over traditional monolithic web development, and demonstrates a practical implementation using Vue, Node.js, and Express for a movie ticketing system, including mock data handling and deployment tips.
frontendnodejsseparation
0 likes · 8 min read


21CTOJul 19, 2017 · Frontend Development
This article examines the evolving definition of front‑back end separation, critiques traditional SPA models, proposes a responsibility‑based split where the front‑end handles view and controller while the back‑end manages the model, and outlines a NodeJS‑driven full‑stack solution with practical implementation insights.
full-stacknodejsseparation
0 likes · 16 min read


21CTOFeb 18, 2017 · Frontend Development
This article examines common misconceptions and pitfalls of front‑end/back‑end separation, explains why proper preparation and clear API design are essential, and outlines practical steps—from project planning to testing and deployment—to implement a successful separation strategy in modern web development.
APIBackendarchitecture
0 likes · 6 min read

The discussion explores various perspectives on front‑back end separation, covering definitions, benefits, architectural patterns, technology choices like Node.js, Vue, Angular, and practical considerations such as API design, performance, and deployment strategies.
APIBack-endFront-end
0 likes · 9 min read
