The Design and Research of Front-End Framework For Microservice Environment
The Design and Research of Front-End Framework For Microservice Environment
net/publication/343250124
CITATIONS READS
7 645
5 authors, including:
Yu Ding
Meta-Sophia Research Institute
19 PUBLICATIONS 38 CITATIONS
SEE PROFILE
All content following this page was uploaded by Yu Ding on 19 November 2020.
Abstract—With the deepening of the software design model of enables the application of multi-tenant, multi-type data source
microservice, the core idea is to separate the business logic of the binding and graphical and information components, providing
front end and the back end. The traditional background logic a design idea with high efficiency and suitability for agile
processing and front-end development of information system are development [3].Ethan Marcottee presents a responsive layout
closely combined, and the processing of the back-end platform as a that effectively solves the compatibility of the website with
whole structure, resulting in the difficulty of the overall multiple terminals and the adaptive front-end design problem
development, long development cycle, and high application [4].The above studies all solve the problem of front-end's
coupling. Based on the component-based front-end design, this
adaptability to different business from their respective
paper proposes a flat front-end framework design idea based on the
perspectives, but none of them give a front-end framework
component concept, and analyzes the application of the framework
and the key technologies of the group. Finally, the front-end
design suitable for micro-service environment. With the advent
framework is applied to the construction of large-scale platform, of excellent front-end models such as React and Angular, front-
which verifies the efficiency and scalability of the framework, and end componentization has gradually become the most urgent
provides a perfect solution for the later complex integration projects. need for front-end development. How to apply these methods
reasonably so that it can improve the efficiency of front-end
Keywords-Microservice; Front-End Framework Model;Design development and reduce maintenance costs has become the
Standards. direction of our research. Based on the above background, this
paper builds a design model based on front-end component,
I. INTRODUCTION puts forward the concept of flattened component structure, and
analyzes the key technologies such as application and group in
In the development of large software systems today, the this framework. Finally, a set of practical front-end framework
front and back ends of Web applications have started to structure is formed, which can be widely used in various micro-
separate. Project teams are required not only to design high- service-based applications.
performance, modular, and flattened application systems, but
also to have low coupling and good iteration capabilities in the
later stage of operation and maintenance. Traditional software II. FRONT-END FRAMEWORK MODEL DESIGN
architecture design ideas have evolved from sophisticated
A. Design standard
SOAP and XML-RPC to Representational State Transfer
(REST), proposed by Dr. Roy Fielding. With REST, a popular From the development trend of software design, a good
development approach for large-scale network application product cannot be separated from the front-end framework
design, the logical processing of the back-end has evolved into model standard of the bottom design. Take the current
a service cluster formed by many small services. On the front mainstream MVC classic framework for example [5]. It is
end, as the business grows or changes, the complexity of the designed to organize code in a way that separates business
system will increase exponentially. Traditional front-end logic, data, and interface display, aggregating business logic
design ideas are based on the business logic of the back-end, so into a single component so that no business logic needs to be
most of the time it is caused by a small change or the increase rewritten when changing business requirements or
of new functions that results in the modification of the overall personalizing. Over time, developers find it difficult to modify
structure. For this problem, there has been some exploration in components in these (ExtJS, miniUI) JS frameworks, so they
the industry, breaking down a large and complex application want to be able to easily customize some components. At this
scenario into small parts that can be disassembled, do not time, JS technology represented by Angular and React that can
interfere with each other, and can be independently developed customize components appeared [6][7]. The emergence of
and maintained. Using the combination of WebGIS and RIA these technologies not only allows developers to customize
technology, the client system is layered by MVC to improve components, but also allows developers to encapsulate
the interactivity and user experience of the system [1].From the components that already exist.
perspective of routing mode, the single page routing problem is On the basis of these studies, the project team has defined
changed and promoted so that the call problem between front- design standards for front-end frameworks based on actual
end pages is solved [2].The front-end framework of WLS
project experience, which require developers and business Figure 1. Front Frame Model Design
personnel to implement framework design for a microservice
environment. Specific criteria are as follows: The model is based on the underlying architecture design of
the platform. The concept of group is applied to the specific
business allocation, a class of users with common
TABLE I. FRONT END FRAME DESIGN STANDARDS characteristics are defined, and then the decentralized
Essential factor describe components and page layout schemes are associated through a
Any component should adhere to a set of group of applications. Finally, a front-end framework structure
development standards, including input and output with group as the core, application as the interactive window
Standardization
definitions, that enable developers of different and component as the basis is formed.
modules to develop unified components.
Most components should be composable. An Take Figure 2 for example. In the HSE group, firstly, it
application must rely on combinations, nesting, and defines the configuration items of the group, such as personnel,
communication between different components. The
Combinatorial
final morphology can also be interpreted as one
roles and menus. Secondly, through the business requirements
HTML fragment by one, which is aggregated of app, the required filling components and audit components
reasonably to form a complete interface display. are combined to form a complete application page. Then the
Since there is a uniform definition of development query page and the notification page are combined with the
standards, any component should be required to be same design idea. Finally, a complete front-end design scheme
Reusability
an individual that can be applied in different of conference room reservation application is formed. Through
scenarios.
Any component should have its own complete and
this flat design idea, the front-end framework has more flexible
stable function, containing only its own logic, which combination ability and agile replacement foundation, and has
Maintainability is not related to other components, making it easier good adaptability and classification on the user's behavior
to understand, making it easier to understand, and operation.
greatly reducing the chance of bugs.
As shown in the table above, all design standards focus on
how to build standard definitions in a microservice
environment, improve code reusability and maintainability, and
address the depth and breadth of software design issues in an
increasingly complex business environment.
ACKNOWLEDGMENT
This research is based on the theory proposed by Dr. Qiao
Dexin. During the research, Dr. Qiao gave us the whole process
of guidance and technical support, and provided a lot of help
when we met difficulties. At the same time, I would like to
thank the information management department of the group
Figure 5. Release Process Diagram
company for their support and once again for their efforts in
this project.