In the SaaS development I work on, there is a fairly high demand for development efficiency. From project initiation, prototype design and evaluation, requirements confirmation, frontend design, and backend development through to final acceptance, we complete one iteration in just a few weeks. Guided by agile development, we began rolling

In recent years, with the rise of single-page web applications, all kinds of frameworks have kept emerging. The front end has begun to enter a stage of engineering and componentization. Single-page web technology has expanded the boundaries of the front end, which can now also route and render pages without depending on the back end.

In frontend-backend separated development, when the backend API is not finished, the frontend cannot continue debugging. So that frontend and backend can develop in parallel, the frontend needs a set of API interface environments — this is the Mock API. The diagram below lays out the development flow nicely. Without a Mock data step, frontend-backend integration takes up a great deal of time.