Front-end scaffolding and business development system

Abstract

The application provides a front-end scaffold and a business development system, comprising: an access layer, a service layer and an operation and maintenance layer; the access layer is used for calling services required by a development task from the service layer, and generating a build product according to the services; the build product is a final product obtained after the development task is completed; the service layer is connected with the access layer, and is used for providing the services required by the development task for the access layer; and the operation and maintenance layer is used for publishing and deploying the build product, and performing operation and maintenance monitoring on the build product after the publishing and deploying are completed. The front-end scaffold provided by the scheme of the application enriches the functions of the front-end scaffold, and realizes support for business fields and development fields.

Description

TECHNICAL FIELD

[0001] The present application relates to the communication technology field, and particularly to a front-end scaffolding and a business development system. BACKGROUND

[0002] The front-end scaffolding is a tool built by engineering means, which can quickly build a project basic framework and configuration. The front-end scaffolding provides a simple and fast semi-finished product application for developers by abstracting the basic form of engineering.

[0003] At present, the front-end scaffolding only focuses on the packaging improvement and template construction process of the development side, and does not involve generating a construction product according to a business requirement and a release and deployment process of the construction product. In the above related technology, the function of the front-end scaffolding is relatively single, and cannot support the business field and the development field. SUMMARY

[0004] The present application provides a front-end scaffolding and a business development system, which aims to solve the problem of the relatively single function of the front-end scaffolding.

[0005] In a first aspect, the present application provides a front-end scaffolding, comprising: an access layer, a service layer and an operation and maintenance layer; the access layer is configured to call a service required by a development task from the service layer, and generate a construction product according to the service; the construction product is a final product obtained after the development task is completed; the service layer is connected with the access layer, and is configured to provide the service required by the development task for the access layer; and the operation and maintenance layer is configured to release and deploy the construction product, and perform operation and maintenance monitoring on the construction product after the release and deployment.

[0006] In a possible implementation, the front-end scaffolding further comprises a template layer; the template layer is configured to construct a template required by the development task; and the access layer is connected with the template layer, and is further configured to obtain the template required by the development task from the template layer.

[0007] In a possible implementation, the access layer comprises a transceiving module and a template conversion engine; the transceiving module is configured to send a template request to the template layer; the template request represents the template required by the development task; the template layer is connected with the transceiving module, and is specifically configured to construct the template required by the development task according to the template request, and send the template required by the development task to the transceiving module; and the template conversion engine is connected with the transceiving module, and is configured to convert the template received by the transceiving module into a format applicable to developers.

[0008] In one possible implementation, the access layer further includes a request acquisition module; the request acquisition module is connected to the transceiver module and is used to acquire the template request and transmit the template request to the transceiver module.

[0009] In one possible implementation, the transceiver module is further configured to: send a service selection instruction to the service layer, the service selection instruction representing the service required to generate the build artifact; the service layer is connected to the transceiver module and is specifically configured to return the service required to generate the build artifact to the transceiver module according to the service selection instruction.

[0010] In one possible implementation, the services required for the build artifact include at least one of the following: commands, orchestration, visualization, statistics, and tracking.

[0011] In one possible implementation, the front-end scaffolding further includes: a core layer; the service layer is further configured to send a core function request to the core layer; wherein the core function request represents the core function required by the service currently returned by the service layer to the access layer; the core layer is connected to the service layer and is configured to provide the core function to the service layer according to the core function request.

[0012] In one possible implementation, the core functionality includes at least one of the following: compilation functionality, debugging functionality, build functionality, storage functionality, and rendering functionality.

[0013] In one possible implementation, the front-end scaffolding further includes: a material layer; the template layer is further configured to send a material selection request to the material layer; wherein the material selection request represents the materials required by the template layer to construct the template required by the development task; the material layer is connected to the template layer and is configured to send the materials required by the template layer to the template layer to construct the template required by the development task according to the material selection request.

[0014] In one possible implementation, the material includes at least one of the following: event tracking, component library, interface, documentation, image hosting, configuration, and test suite.

[0015] Secondly, this application provides a business development system, including the front-end scaffolding and the publishing platform as described above; the operation and maintenance layer of the front-end scaffolding is connected to the publishing platform and is used to publish the built products to the publishing platform.

[0016] The front-end scaffolding and the business development system provided in the application, the access layer calls services required by the development task from the service layer, and generates a construction product according to the services; the construction product is a final product obtained after the development task is completed; the service layer is connected with the access layer, and provides services required by the development task for the access layer; the operation and maintenance layer publishes and deploys the construction product, and performs operation and maintenance monitoring on the construction product after the publishing and deployment are completed. The scheme of the application adopts a layered architecture, different layers are constructed based on different business requirements, and each layer is connected in series through a processized manner. On the basis of the layered architecture, the access layer generates a final product obtained after the development task is completed by calling the services in the service layer, and the construction product is deployed and published through the operation and maintenance layer, thereby enriching the functions of the front-end scaffolding and realizing the support for the business field and the development field. BRIEF DESCRIPTION OF DRAWINGS

[0017] The accompanying drawings, which are incorporated herein and form a part of the specification, illustrate embodiments consistent with the present application and, together with the description, further serve to explain the principles of the application.

[0018] Figure 1 A structure schematic diagram of the front-end scaffolding provided for the first embodiment of the application is shown in the figure.

[0019] Figure 2 A structure schematic diagram of the front-end scaffolding provided for the second embodiment of the application is shown in the figure.

[0020] Figure 3 A development process schematic diagram based on the front-end scaffolding provided for the third embodiment of the application is shown in the figure.

[0021] Figure 4 A layered architecture schematic diagram of the front-end scaffolding provided for the third embodiment of the application is shown in the figure.

[0022] The specific embodiments of the application have been shown in the above-described figures, and will be described in more detail hereinafter. These figures and the written description are not intended to limit the scope of the inventive concept in any way, but to illustrate the inventive concept to those skilled in the art by reference to specific embodiments. DETAILED DESCRIPTION

[0023] The exemplary embodiments will be described in detail herein with reference to the attached drawings. The following description is made with reference to the accompanying drawings in which like reference numerals represent like elements, unless the context of use indicates otherwise. The following description of exemplary embodiments is not representative of all embodiments consistent with the present application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of the present application as detailed in the appended claims.

[0024] It should be noted that the brief description of the terms in this application is only for the convenience of understanding the embodiments described below, and is not intended to limit the embodiments of the application. Unless otherwise specified, these terms should be understood according to their ordinary and general meanings.

[0025] The terms "first", "second", and the like in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar or similar objects or entities, and do not necessarily mean a specific order or sequence, unless otherwise indicated. It should be understood that the terms used in this way can be interchanged under appropriate circumstances, for example, those other than the order given in the embodiment illustration or description of the present application can be implemented.

[0026] In addition, the terms "include" and "have" and any variations thereof are intended to cover but not exclusive inclusion, for example, a product or device including a series of components does not have to be limited to those components clearly listed, but can include other components not clearly listed or inherent to these products or devices. The term "module" used in the present application refers to any known or later developed hardware, software, firmware, artificial intelligence, fuzzy logic, or combination of hardware or / and software code capable of performing functions related to the element.

[0027] The front-end scaffold is built by engineering means, which can quickly build the project basic framework and configuration tool. Application of front-end scaffold for business development can reduce repetitive work.

[0028] At present, the front-end scaffold mainly focuses on the packaging improvement and template construction scheme of the development side, which can quickly generate the basic code of the project and build a complete project basic environment in a short time. However, the front-end scaffold function is single, which cannot meet the requirements of development and business background, and lacks unified template tools for engineering convergence regulation.

[0029] The front-end scaffold provided in the embodiments of the present application adopts a layered architecture, builds different layers based on different business needs, and realizes series connection between each layer through a process-based manner. On the basis of the layered architecture, the access layer generates the final product obtained after the development task is completed by calling the services in the service layer, and deploys and publishes the construction product through the operation and maintenance layer, which enriches the functions of the front-end scaffold and realizes the support for business and development fields.

[0030] The technical solutions of the present application and the technical solutions of the present application will be described in detail below with specific examples. The following specific examples can be combined with each other, and the same or similar concepts or processes may not be described again in some examples. In the description of the present application, unless otherwise explicitly specified and limited, each term should be understood broadly in the art. The embodiments of the present application will be described below with reference to the accompanying drawings.

[0031] Embodiment one

[0032] Figure 1 The structural schematic diagram of the front-end scaffold provided by the first embodiment of the present application is shown in Figure 1 The present embodiment provides a front-end scaffold, which comprises an access layer 11, a service layer 12 and an operation and maintenance layer 13.

[0033] In the present embodiment, the access layer 11 is used to call the services required by the development task from the service layer 12, and to generate the build product according to the above-mentioned services; the service layer 12 is connected with the access layer 11, and is used to provide the services required by the development task for the access layer 11.

[0034] Among them, the services required by the development task refer to the functions used to execute the development task, and the services can make the development task more simple and convenient to execute. In actual application, the development task corresponds to the services required by the development task, and after determining the development task, the services required by the development task can be determined according to the development task. For example, the development task is to create a data dashboard to realize data visualization display, and the services required by the development task are visualization, arrangement, statistics and creation, etc.

[0035] It can be understood that the services are general functions required by the development task, and in the actual development process, the general functions can be directly called to realize the services, which saves the time of deploying general functions and improves the development efficiency.

[0036] Among them, the build product is the final product obtained after the development task is completed. In actual application, the build product corresponds to the development task, for example, the development task is to create a web page, and the build product is the created web page. It can be understood that the access layer 11 is used to generate the build product according to the development task, and the build product corresponds to the development task, and the services required by the development task are the services required to generate the build product.

[0037] It should be noted that the developer in the access layer 11 can compile and execute the development task, and cannot directly obtain the services required by the development task from the service layer 12. The developer needs to interact with the service layer 12 through the access layer 11 to call the services required by the development task.

[0038] Optionally, the developer formulates the development task and the service required by the development task according to the actual business requirement, the access layer 11 calls the service required by the development task from the service layer 12, and after obtaining the service required by the development task, the access layer 11 executes the development task according to the service required by the development task to generate the build product.

[0039] Optionally, in an example, the service required by the build product includes at least one of the following: command, orchestration, visualization, statistics, and tracking.

[0040] The command refers to that the command can provide a simplified operation function for the development task, for example, the command provides functions such as creation, testing, release, etc. Optionally, after installing the scaffolding, the command service is registered in the service layer 12 to build the front-end scaffolding.

[0041] The orchestration can be implemented through different integrated development environments (Integrated Development Environment, referred to as IDE) and browser plug-in forms, and supports componentization and modularization drag orchestration of templates. Optionally, the development task can be implemented through multiple microservices, and the microservice refers to that the development task is executed through multiple loosely coupled and independently deployable smaller components or services. The combination relationship and execution order of multiple microservices can be designed through the orchestration service.

[0042] The visualization refers to organizing data information and presenting it in a graphical way. Optionally, the visualization service can determine the graphical shape and color information corresponding to the data information, so as to realize the conversion of the data information into a graph for presentation.

[0043] In practical applications, the panel supports the data panel in the front-end scaffolding creation process, presents the data and charts related to the current business or operation and management, and outputs the data analysis report through the statistics function, so as to facilitate the monitoring of the development task. The tracking refers to providing link retrieval and query, and can realize data retrieval and query. Optionally, the service required by the build product can be extended according to the business requirement, which is not limited here.

[0044] In this embodiment, the operation and maintenance layer 13 is configured to release and deploy the build product, and to perform operation and maintenance monitoring on the build product after the release and deployment.

[0045] The deployment refers to uploading the code corresponding to the build product to the cloud storage. It can be understood that the operation and maintenance layer 13 can realize uploading the code corresponding to the build product to the cloud storage, thereby realizing the release of the build product. In practical applications, when the build product is deployed, the operation and maintenance monitoring link can be set, and the developer can perform operation and maintenance monitoring on the build product after the release and deployment through the operation and maintenance monitoring link.

[0046] It should be noted that the front-end scaffolding adopts a layered structure, and different architecture modes can be combined for use inside each structural layer. For example, different architecture models such as hexagon architecture and onion architecture are combined for use to build the connection and association of the atomization capabilities between modules. Different association methods can be used to connect the layers in a process-based manner, thereby providing developers with more convenient and efficient services. For example, each layer can be a microservice, and the concatenation of microservices is used to achieve the concatenation between layers.

[0047] In this embodiment, the front-end scaffolding adopts a layered architecture, and different layers are built based on different business requirements. The layers are connected in a process-based manner, and on the basis of the layered architecture, the access layer accesses the services in the service layer to generate the final product obtained after the development task is completed, and the operation and maintenance layer deploys and releases the build product, thereby enriching the functions of the front-end scaffolding and supporting the business and development fields.

[0048] Optionally, the service layer 12 returns services to the access layer 11, which requires support of core functions. In a possible implementation, the front-end scaffolding further includes a core layer.

[0049] The service layer 12 is further configured to send a core function request to the core layer.

[0050] The core layer is connected with the service layer 12 and is configured to provide core functions to the service layer 12 according to the core function request.

[0051] The core layer is the core part of the front-end scaffolding and is configured to provide core support for the services in the service layer 12. The core functions are the functions of the bottom layer of the front-end scaffolding. The core function request represents the core functions required by the services returned by the service layer 12 to the access layer 11.

[0052] In actual applications, the core function request can correspond to multiple core functions. For example, the services returned by the service layer 12 to the access layer 11 are statistical services, and the core function request corresponds to the functions of building, storing, and compiling.

[0053] It can be understood that when the service layer 12 needs to return services to the access layer 11, the service layer 12 sends a core function request to the core layer, the core layer provides core functions to the service layer 12 according to the core function request, and the service layer 12 returns the services required by the development task to the access layer 11 based on the core functions provided by the core layer.

[0054] In this embodiment, the service layer obtains the core function provided by the core layer by sending a core function request to the core layer, and based on the support of the core function, the service layer implements the service required for the development task of the access layer.

[0055] Optionally, in a possible implementation, the core function includes at least one of the following: a compilation function, a debugging function, a build function, a storage function, and a rendering.

[0056] The compilation function refers to constructing an abstract syntax tree (AST) by abstracting into a unified internal static single assignment (SSA) syntax form, to implement relevant syntax conversion on codes written in different syntaxes. For example, the compilation function includes just-in-time compilation (JIT), ahead-of-time compilation (AOT), and relevant performance optimization on a compiler, without limitation.

[0057] The debugging function refers to supporting a developer to perform breakpoint debugging, code positioning, and error output interception on corresponding codes. Optionally, the debugging function can also provide plug-in support for different integrated development environments.

[0058] The build function refers to supporting compression and optimization of codes. The build function supports general-purpose packaging and building. For example, the build function supports Webpack, Esbuild, and other general-purpose packaging tools for packaging and building. Optionally, the build function supports custom packaging and building. For example, a cross-language form such as go or rust can be used for corresponding packaging and building.

[0059] The storage function refers to supporting different storage settings for separation of dynamic and static resources. Different storage forms such as object storage, file storage, and hard disk can be used to perform relevant separation settings on front-end resources.

[0060] The rendering refers to rendering and distribution of corresponding front-end resources based on different business forms and in cooperation with the storage function. For example, the rendering can be browser rendering (CSR), server-side rendering (SSR), native rendering (NSR), and edge rendering (ESR).

[0061] The front-end scaffold provided in the embodiment includes an access layer, a service layer and a maintenance layer.

[0062] Embodiment Two

[0063] Figure 2 A structure diagram of the front-end scaffold provided in Embodiment Two of the present application is shown in FIG. 2. Figure 2 As shown in FIG. 2, the front-end scaffold provided in the embodiment further includes a template layer 21.

[0064] In the embodiment, the template layer 21 is configured to build templates required by a development task; and the access layer 11 is connected to the template layer 21 and further configured to obtain the templates required by the development task from the template layer 21.

[0065] The templates required by the development task refer to frameworks for executing the development task, and the development can be performed based on the templates required by the development task. For example, the templates can be projects with basic environments and parameter configurations, and the development task can be performed based on the templates, thereby saving the steps of establishing the projects, environment configuration and parameter configuration.

[0066] In actual applications, the template layer 21 can build different template schemes according to different business requirements, and the templates in the template layer 21 can be updated and iterated according to changes in actual business requirements. For example, the business requirement is a backstage direction, which mainly provides management-related front-end applications for users of the management type, and the layout strategy is mainly considered in the template building process. For example, the business requirement is a large-screen direction, which mainly provides visual data display for users of the general type, and the product intuitive expression is mainly considered in the template building process. For example, the business requirement is a cross-end direction, and the key is one-key development and adaptation for different ends, and the system uniformity and stability are mainly considered in the template building process.

[0067] Optionally, the template layer 21 supports the construction of custom templates, and can build templates required by users according to the requirements of the users, thereby improving the inclusiveness and scalability of the development.

[0068] It should be noted that the developer cannot directly obtain the template required for development from the template layer 21, and the template required for the development task is obtained from the template layer by accessing the access layer 11. It can be understood that if the template required for the development task is in the template layer 21, the template required for the development task can be directly pulled from the template layer by the access layer 11; if the template required for the development task is not in the template layer 21, the template layer 21 can build the template required for the development task and send the template required for the development task to the access layer 11.

[0069] In this embodiment, the access layer 11 obtains the template required for the development task from the template layer 21, and develops on the basis of the template required for the development task, which can improve the efficiency of development.

[0070] Optionally, regarding the process of obtaining the template required for the development task, in a possible implementation manner, the access layer 11 comprises a transceiver module and a template conversion engine;

[0071] The transceiver module is configured to send a template request to the template layer 21;

[0072] The template layer 21 is connected with the transceiver module, and is specifically configured to build the template required for the development task according to the template request, and send the template required for the development task to the transceiver module;

[0073] The template conversion engine is connected with the transceiver module, and is configured to convert the template received by the transceiver module into a format applicable to the developer.

[0074] The template request represents the template required for the development task, and the transceiver module sends the template request to the template layer 21 to obtain the template required for the development task from the template layer 21. The template layer 21 builds the template corresponding to the template request based on the received template request, and sends the built template to the transceiver module.

[0075] In actual application, the template conversion engine inserts a dynamic node placeholder into the template received by the transceiver module to convert the template received by the transceiver module into a format applicable to the developer. Optionally, the template received by the transceiver module is a custom template, and the template conversion engine needs to compile and convert the custom template.

[0076] In this embodiment, the transceiver module sends a template request to the template layer, the template layer builds the template required for the development task according to the template request, and sends the template required for the development task to the transceiver module, and the module conversion engine converts the template received by the transceiver module into a format applicable to the developer, and develops based on the converted template, which improves the efficiency of development.

[0077] Optionally, for the template request acquisition, in a possible implementation, the access layer 11 further includes a request acquisition module.

[0078] The request acquisition module is connected with the transceiver module, configured to acquire the template request and transmit the template request to the transceiver module.

[0079] In actual application, if the template layer 21 has the template required by the development task, the request acquisition module can directly acquire from the storage tool. For example, the storage tool can be a distributed version control system or a centralized version control system. If the template layer 21 does not have the template required by the development task, the request acquisition module acquires the customized template request.

[0080] In the embodiment, the request acquisition module dynamically acquires the template request according to the template required by the development task, so as to facilitate the transceiver module to pull the template required by the development task from the template layer based on the template request.

[0081] In addition, in a possible implementation, the transceiver module is further configured to:

[0082] send a service selection instruction to the service layer 12;

[0083] The service layer 12 is connected with the transceiver module, and is specifically configured to return, to the transceiver module, a service required for generating the build product according to the service selection instruction.

[0084] The service selection instruction represents the service required for generating the build product. It can be understood that the transceiver module sends the service selection instruction to the service layer 12 to call the service in the service layer 12 to generate the service required for generating the build product, so that the access layer 11 generates the build product based on the service required for generating the build product.

[0085] In the embodiment, the transceiver module achieves calling the service required for generating the build product from the service layer by sending the service selection instruction to the service layer.

[0086] Optionally, the template layer 21 needs to select materials for building the template, and in a possible implementation, the front-end scaffolding further includes a material layer.

[0087] The template layer 21 needs to send a material selection request to the material layer.

[0088] The material layer is connected with the template layer 21, and is configured to send, to the template layer 21, materials required for building the template required by the development task according to the material selection request.

[0089] The material selection request represents the materials required by the template layer 21 to build the template required by the development task. In actual application, when the template layer 21 builds the template required by the development task, a material selection request is sent to the material layer, the materials required by the template required by the development task are selected, and the material layer 21 builds the template required by the development task based on the materials sent by the material layer.

[0090] It can be understood that based on the support of the material layer, the template layer 21 can implement the construction of the custom template and the template corresponding to the business requirement.

[0091] Optionally, in an example, the above-mentioned material includes at least one of the following: a buried point, a component library, an interface, a document, a picture bed, a configuration, and a test suite.

[0092] The material refers to a basic function service that can support the basic front-end development. In this example, the material layer provides a software development kit (Software Development Kit, SDK) access service for data burying, and also supports log tracking and large plate visualization of the overall data. Optionally, the material layer provides a component library function. For example, the component library can be a general component library; the component library can also be a custom or business component library. Optionally, the material layer provides interface conversion, aggregation and other related intermediate layer functions. Optionally, the material layer provides standardized documents to facilitate development, learning, understanding and code constraints. Optionally, the material layer provides a picture bed to facilitate the uploading and viewing of image resources. Optionally, the material layer provides a configuration platform to facilitate the configuration of common fields. Optionally, the material layer provides a test suite to facilitate the automatic generation of unit test files, etc.

[0093] In the front-end scaffold provided in this embodiment, the template layer builds the template required by the development task; and the access layer is connected with the template layer and obtains the template required by the development task from the template layer. The front-end scaffold of this embodiment obtains the template required by the development task from the template layer by the access layer, and develops on the basis of the template required by the development task, thereby effectively improving the development efficiency.

[0094] Embodiment Three

[0095] Figure 3 A development process schematic diagram based on the front-end scaffold is provided for the third embodiment of the present application. The front-end scaffold provided in this embodiment includes an access layer, a template layer, a service layer, a core layer, a material layer, and an operation and maintenance layer. As shown in Figure 3 The execution process of a development task is taken as an example, which includes the following steps:

[0096] S301, the access layer sends a template request to the template layer;

[0097] S302, the template layer sends a material selection request to the material layer;

[0098] S303, the material layer sends the material required by the template layer to build the template required by the template layer to the template layer according to the material selection request;

[0099] S304, the template layer builds the template required by the development task based on the received material;

[0100] S305, the template layer sends the template required by the development task to the access layer;

[0101] S306, the access layer sends the service selection instruction to the service layer;

[0102] S307, the service layer sends the core function request to the core layer;

[0103] S308, the core layer provides the core function to the service layer;

[0104] S309, the service layer returns the service required to generate the construction product to the access layer;

[0105] S310, the access layer generates the construction product according to the received service;

[0106] S311, the release deployment construction product;

[0107] S312, the operation and maintenance monitoring is carried out on the construction product which completes the release deployment.

[0108] Wherein, the template request represents the template required by the development task. It can be understood that the template layer determines the template required by the development task to be built and the material corresponding to the template required by the development task to be built according to the template request sent by the access layer, and sends the material selection request to the material layer, the material selection request is used to request the material corresponding to the template required by the development task to be built from the material layer. The material layer sends the material required by the template layer to build the template required by the template layer to the template layer according to the material selection request. The template layer builds the template required by the development task based on the received material. The template layer sends the template required by the development task to the access layer.

[0109] In practical application, the access layer receives the template required by the development task sent by the template layer, and develops based on the template required by the development task. It can be understood that the construction product is the final result of the execution of the development task, and the process of generating the construction product is the execution process of the development task, and the service in the service layer needs to be called to execute the development task.

[0110] The service selection instruction represents a service required for generating the build product. The access layer sends the service selection instruction to the service layer. After receiving the service selection instruction, the service layer returns the service required for generating the build product to the access layer. It should be noted that the service in the service layer needs to be supported by the core function in the core layer. Therefore, the service layer returns the service required for generating the build product to the access layer, and needs to call the core function corresponding to the service required for generating the build product in the core layer.

[0111] To facilitate understanding of the layered structure of the front-end scaffolding, the following is an example of a layered structure of the front-end scaffolding. Figure 4 Figure 4 The layered architecture of the front-end scaffolding provided in Embodiment Three is shown in FIG. 3. Figure 4 As shown in FIG. 3, the front-end scaffolding includes an access layer, a template layer, a service layer, a core layer, a material layer, and an operation and maintenance layer.

[0112] The template layer supports templates corresponding to the business requirements of the background, large screens, and cross-end. The template layer also supports user-defined third-party template construction. The access layer includes a template conversion engine and a storage tool, and the storage tool is used to store template requests. The service layer includes commands, orchestration, visualization, statistics, and tracking services. The core layer includes core functions such as compilation, debugging, building, storage, and rendering. The material layer includes a point-in-time, component library, interface, document, image bed, configuration, and test suite. The operation and maintenance layer supports cloud platforms, servers, and virtual machines for publishing platforms.

[0113] In actual applications, developers can directly publish and deploy the generated build product through the operation and maintenance layer. For example, the code corresponding to the build product is uploaded to the cloud storage through the operation and maintenance layer, and the parameters corresponding to the build product are set in the operation and maintenance layer to achieve the deployment and publication of the build product. For example, the address of the build product and the time of the build product are set in the operation and maintenance layer.

[0114] In the front-end scaffolding provided in this embodiment, the access layer calls the service required for the development task from the service layer, and generates a build product according to the service. The build product is the final product obtained after the development task is completed. The service layer is connected with the access layer, and provides the service required for the development task for the access layer. The operation and maintenance layer publishes and deploys the build product, and performs operation and maintenance monitoring on the build product after the publication and deployment. The front-end scaffolding of this embodiment adopts a layered architecture, builds different layers based on different business requirements, and realizes the connection between each layer through a process-based manner. On the basis of the layered architecture, the service in the service layer is called through the access layer to generate the final product obtained after the development task is completed. The build product is deployed and published through the operation and maintenance layer, which enriches the functions of the front-end scaffolding and realizes the support for the business field and the development field.

[0115] Embodiment Four​

[0116] The embodiment four provides a service development system, comprising the front-end scaffold and the publishing platform of the foregoing embodiments.

[0117] In the embodiment, the operation and maintenance layer of the front-end scaffold is connected with the publishing platform, and is configured to publish the build product to the publishing platform. The publishing platform can be a cloud platform, a server, or a virtual machine.

[0118] Optionally, the publishing platform can be a cloud platform of different manufacturers, and the operation and maintenance layer of the front-end scaffold can realize cloud-based deployment of the build product based on the business requirements of the manufacturers, so as to publish the build product to the cloud platform. Optionally, the publishing platform can also be a server, and the operation and maintenance layer of the front-end scaffold can support deployment of a private server. For example, a network transmission form between the operation and maintenance layer and the server can be deployed in the operation and maintenance layer of the front-end scaffold. Optionally, the publishing platform is a virtual machine, and the operation and maintenance layer of the front-end scaffold can support server deployment of a distributed system.

[0119] It can be understood that the operation and maintenance layer performs operation and maintenance monitoring on the build product after deployment and publishing, and in essence, the operation and maintenance layer performs operation and maintenance monitoring on the build product published to the publishing platform. For example, an operation and maintenance monitoring link corresponding to the publishing platform can be deployed in the operation and maintenance layer, so as to perform operation and maintenance monitoring on the build product published to the publishing platform.

[0120] For example, when a developer needs to perform a development task and publish a build product to a publishing platform, the access layer calls services required by the development task from the service layer, and generates the build product according to the received services. The build product is deployed and published in the operation and maintenance layer, so as to publish the build product to the publishing platform and perform operation and maintenance monitoring on the build product published to the publishing platform.

[0121] In the service development system provided in the embodiment, the access layer calls services required by the development task from the service layer, and generates the build product according to the services. The build product is the final product obtained after the development task is completed. The service layer is connected with the access layer, and provides services required by the development task for the access layer. The operation and maintenance layer publishes the build product to the publishing platform, and performs operation and maintenance monitoring on the build product after deployment and publishing. The service development system in the embodiment generates the final product obtained after the development task is completed by calling the services in the service layer through the access layer, and deploys and publishes the build product through the operation and maintenance layer, thereby enriching the functions of the front-end scaffold and realizing support for the business field and the development field.

[0122] Other embodiments of the application will be apparent to those skilled in the art from consideration of the specification and practice of the application disclosed herein. It is intended that the specification and examples be considered as exemplary only, with the true scope and spirit of the application being indicated by the following claims.

[0123] It is to be understood that the application is not limited to the precise construction herein disclosed and shown in the drawings, and that various changes in shape, size and arrangements of parts can be made without departing from the scope of the application. The scope of the application is limited only by the claims that follow.

Claims

1. A front-end scaffold characterized by, The application relates to a system and method for constructing a development task, and belongs to the technical field of software development. The system comprises an access layer, a service layer, an operation and maintenance layer, a template layer, a core layer and a material layer. The access layer comprises a transceiving module and a template conversion engine. The transceiving module is used for sending a template request to the template layer, wherein the template request represents a template required by a development task, the template is a project for completing basic environment and parameter configuration, and the transceiving module is also used for obtaining the template required by the development task from the template layer. The template layer is used for sending a material selection request to the material layer according to the template request, wherein the material selection request represents materials required by the template layer for constructing the template required by the development task, the materials comprise at least one of the following: a burying point, a component library, an interface, a document, a picture bed, a configuration and a test suite, the material layer is connected with the template layer, and the material layer is used for sending the materials required by the template layer for constructing the template required by the development task to the template layer according to the material selection request. The template layer is connected with the transceiving module, and is specifically used for constructing the template required by the development task according to the materials required by the template layer for constructing the template required by the development task, and sending the template required by the development task to the transceiving module. The template conversion engine is connected with the transceiving module, and is used for inserting dynamic node placeholders into the template received by the transceiving module, so as to convert the template received by the transceiving module into a format applicable to developers. The access layer is used for calling a service required by a development task from the service layer, and generating a construction product according to the service based on the template in the format applicable to developers, wherein the construction product is a final product obtained after the development task is completed. The service layer is connected with the access layer, and is used for providing the service required by the development task for the access layer, the service required by the construction product comprises at least one of the following: a command, an arrangement, a visual effect, statistics and tracking, and the service layer is also used for sending a core function request to the core layer, wherein the core function request represents a core function required by the service returned by the service layer to the access layer. The core layer is connected with the service layer, and is used for providing a core function for the service layer according to the core function request, wherein the core function comprises at least one of the following: a compiling function, a debugging function, a construction function, a storage function and a rendering function. The operation and maintenance layer is used for publishing and deploying the construction product to a publishing platform, and setting an operation and maintenance monitoring link when the construction product is deployed, and performing operation and maintenance monitoring on the construction product after the publishing and deployment are completed, wherein the publishing platform comprises a cloud platform, a server or a virtual machine, and the server comprises a private server.

2. The front-end scaffolding of claim 1, wherein, The access layer further comprises a request obtaining module. The request obtaining module is connected with the transceiving module, and is used for obtaining the template request and transmitting the template request to the transceiving module.

3. The front-end scaffolding of claim 1, wherein, The transceiving module is also used for: sending a service selection instruction to the service layer, wherein the service selection instruction represents a service required for generating the construction product. The service layer is connected with the transceiving module, and is specifically configured to return the service required for generating the build product to the transceiving module according to the service selection instruction.

4. A business development system, characterized by, Comprise: The front-end scaffold and the publishing platform according to any one of claims 1-3; The operation and maintenance layer of the front-end scaffold is connected with the publishing platform, and is configured to publish the build product to the publishing platform.

Images