Schedule management system design method and device based on distributed platform

Abstract

The invention discloses a schedule management system design method and device based on a distributed platform, and belongs to the field of system design. The method comprises the following steps: establishing an initial schedule management system based on a JAVA language according to a SpringBoot framework; using an Nginx server to carry out service proxy and load balancing on the initial schedule management platform; and performing interface debugging on the initial schedule management system by using a Swagger interface document to obtain a final schedule management system. According to the method, the service performance can be well improved, the situation that the user experience is influenced by project crashing caused by large request pressure of a program is avoided, and the problems of high concurrency, low performance and low reliability of related technologies are solved.

Description

Technical Field

[0001] The present invention relates to the technical field of system design, and in particular to a method and device for designing a schedule management system based on a distributed platform. Background Art

[0002] A schedule management system is a tool used to plan, track and manage individual or team schedules. It can help users effectively arrange time, set reminders, record important events, and optimize workflows. It is one of the indispensable tools in modern life and plays an important role in team collaboration.

[0003] Existing schedule management systems are usually designed and implemented based on Apache servers. However, when using this server to design a schedule management system, it often faces problems such as high access pressure, high concurrency, low performance and low reliability.

[0004] Based on this, there is an urgent need for a distributed platform-based schedule management system design method and device to solve the above technical problems. Summary of the invention

[0005] The present invention provides a method and device for designing a schedule management system based on a distributed platform, which can solve the problems of high concurrency, low performance and low reliability in related technologies. The technical solution is as follows:

[0006] On the one hand, a method for designing a schedule management system based on a distributed platform is provided, the method comprising:

[0007] Establish an initial schedule management system based on JAVA language according to the SpringBoot framework;

[0008] Using Nginx server to perform service proxy and load balancing on the initial schedule management platform;

[0009] The initial schedule management system is debugged using the Swagger interface document to obtain the final schedule management system.

[0010] On the other hand, a distributed platform-based schedule management system design device is provided, the device comprising:

[0011] Building module, used to build the initial schedule management system based on JAVA language according to SpringBoot framework;

[0012] A management module, used for performing service proxy and load balancing on the initial schedule management platform by using an Nginx server;

[0013] The debugging module is used to use the Swagger interface document to perform interface debugging on the initial schedule management system to obtain the final schedule management system.

[0014] On the other hand, a computer device is provided, which includes a memory and a processor, wherein the memory is used to store computer programs, and the processor is used to execute the computer programs stored in the memory to implement the steps of the above-mentioned method for designing a schedule management system based on a distributed platform.

[0015] On the other hand, a computer-readable storage medium is provided, wherein a computer program is stored in the storage medium, and when the computer program is executed by a processor, the steps of the above-mentioned method for designing a schedule management system based on a distributed platform are implemented.

[0016] On the other hand, a computer program product is provided, including a computer program, which implements the steps of the above-mentioned method for designing a schedule management system based on a distributed platform when executed by a processor.

[0017] The technical solution provided by the present invention can at least bring the following beneficial effects: by using Eclipse-based STS (Spring Tools Suite) as a development platform, using the Spring Boot framework and MySQL database for development, and matching the distributed system platform to integrate the schedule calendar into a management system, by using the Nginx proxy server to implement the reverse proxy and load balancing of the service, the Swagger interface document is also integrated in it, which can be used to manage and test interface problems for easy debugging, making it more suitable for user groups and eliminating the troubles of users using multiple systems. The method can improve service performance by using nginx to implement service load balancing and service proxy. Avoid the occurrence of large program request pressure causing the project to crash and affect the user experience, and solve the problems of high concurrency, low performance, and low reliability of related technologies. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0019] Figure 1 It is a flow chart of a method for designing a schedule management system based on a distributed platform provided by an embodiment of the present invention;

[0020] Figure 2This is an initial framework diagram of a schedule management system based on an Nginx server provided by an embodiment of the present invention;

[0021] Figure 3 This is a schematic diagram of a login interface of a schedule management system provided by an embodiment of the present invention;

[0022] Figure 4 This is a schematic diagram of the main interface of a schedule management system provided by an embodiment of the present invention;

[0023] Figure 5 It is a structural diagram of a schedule management system design device based on a distributed platform provided by an embodiment of the present invention;

[0024] Figure 6 It is a hardware architecture diagram of a computer device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0025] In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, rather than all the embodiments. Based on the embodiments in the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0026] As mentioned above, existing schedule management systems are usually designed and implemented based on Apache servers. However, when using such servers to design schedule management systems, they often face problems such as high access pressure, high concurrency, low performance and low reliability.

[0027] Based on this, the idea of ​​the present invention is to realize reverse proxy by using Nginx with a server, set different ports for multiple programs, and then connect them through the proxy server Nginx to achieve load balancing.

[0028] The specific implementation of the above concept is described below.

[0029] Please refer to Figure 1 , an embodiment of the present invention provides a method for designing a schedule management system based on a distributed platform, the method comprising:

[0030] Step 100, establishing an initial schedule management system based on JAVA language according to the SpringBoot framework;

[0031] Step 102, using Nginx server to perform service proxy and load balancing on the initial schedule management platform;

[0032] Step 104: Use the Swagger interface document to debug the interface of the initial schedule management system to obtain the final schedule management system.

[0033] In the embodiment of the present invention, by using Eclipse-based STS (Spring Tools Suite) as a development platform, using the Spring Boot framework and MySQL database for development, and matching the distributed system platform to integrate the schedule calendar into a management system, by using the Nginx proxy server to implement the reverse proxy and load balancing of the service, the Swagger interface document is also integrated in it, which can be used to manage and test interface problems for easy debugging, making it more suitable for user groups and eliminating the troubles of users using multiple systems. The method can improve service performance by using nginx to implement service load balancing and service proxy. Avoid the occurrence of large program request pressure causing the project to crash and affect the user experience, and solve the problems of high concurrency, low performance, and low reliability of related technologies.

[0034] Described below Figure 1 How the various steps are performed.

[0035] First, with respect to step 100, an initial schedule management system based on JAVA language is established according to the SpringBoot framework.

[0036] The schedule management system is a simple schedule management platform based on Java. It uses the Eclipse-based STS (Spring Tools Suite) as the development platform, the Spring Boot framework and the MySQL database to develop, and integrates the schedule calendar into a management system with a distributed system platform.

[0037] Specifically, the SpringBoot framework includes dao layer, service layer, controller layer and html layer, among which: the dao layer is used to assist in removing data from the database; the controller layer is the business layer and the view layer responsible for html interface development; the controller layer is used to pass the data obtained from the service layer to the html page, and then carry the data to the html page to be jumped.

[0038] Then, for step 102, the Nginx server is used to perform service proxy and load balancing on the initial schedule management platform.

[0039] In an embodiment of the present invention, the Nginx server is used to perform service proxy for the initial schedule management platform, including: starting the Nginx server to read the configuration file of the initial schedule management system and writing user information into the configuration file; defining a request class according to user needs, and using the server to execute a corresponding type of data request according to the read request information, thereby obtaining a basic framework of the service proxy.

[0040] Specifically, first, the server is started, and then the server reads the configuration file. Next, the user's account password and other information are written into the configuration file. When the client and the server are connected, data requests are required, which include multiple request types. The requests included here include user registration and login requests, schedule addition, deletion, modification and query requests, personal diary addition, deletion, modification and query requests, anniversary addition, deletion, modification and query requests, recycle bin recovery and deletion requests, and user logout requests. To meet the above requirements, we need to define a request class and require the server to continuously read the request information. This is what happens. Figure 2 The basic framework of the server is shown.

[0041] like Figure 3 and Figure 4 As shown, the user chooses to register or log in. If the user chooses to register, he / she should choose to log in after the registration is completed. After successful login, the user will enter the main interface, where the user can add, delete, modify and check the schedule, and can also choose to add personal diaries, add anniversaries, and recycle bins, search schedules, etc. Finally, the user can choose to log out of the user to exit the personal account or close the client to end this login.

[0042] In an embodiment of the present invention, the initial schedule management platform is load balanced by using an Nginx server, including: using Java to write a load balancer for listening to requests on a specified port and forwarding the requests to the server; configuring the address and port of the server in the http part, and configuring the backend service address of the load balancer in the server part; accessing the address of the Nginx server through a browser, refreshing the browser page multiple times while observing the log output of the load balancer, and determining that the load balancing is successful when the output result meets the preset conditions.

[0043] Specifically, first install the Nginx server and make sure it runs correctly. Then, use Java to write a load balancer that listens to requests on the specified port and forwards the requests to the server. Then configure the address and port in the http part, and configure the backend service address of the load balancer in the server part. Finally, open the browser, visit the address of the Nginx server, refresh the page multiple times, observe the log output of the Java project, and adjust it according to the output results until the load balance is satisfied.

[0044] With respect to step 104, the initial schedule management system is interface debugged using the Swagger interface document to obtain a final schedule management system.

[0045] Swagger interface documentation has the following advantages:

[0046] Rich functions: supports multiple annotations, automatically generates interface documentation interface, and supports testing API interface functions on the interface;

[0047] Timely updates: Spend a little time writing comments during the development process, so that you can update the API documentation in a timely manner, saving you time and effort;

[0048] Simple integration: By adding pom dependencies and simple configuration, the API interface document interface can be published simultaneously when embedded in the application without the need to deploy independent services.

[0049] In an embodiment of the present invention, the debugging process includes importing a pre-built Swagger interface document into the initial schedule management system and entering the interface of the Swagger interface document; inputting parameters into the test interface of the preset controller in the Swagger interface document, and debugging the initial schedule management system according to the output results to obtain the final schedule management system.

[0050] Specifically, first open the browser and visit: Spring Initializr official website, then select the build tool, development language, project information, etc. according to the page prompts, then click Generate the project to generate the project template. After generation, the compressed package will be downloaded to the local, and finally use IDE to import the project. This embodiment uses Eclipse and imports it by importing the Maven project.

[0051] The specific import process includes: adding Maven related dependencies, here you need to add WEB and SWAGGER dependencies. Then add a swagger configuration class, create a new config package under the project and add a SwaggerConfig configuration class: SwaggerConfig.java. Right-click the file DemoApplication.java->Runas->JavaApplication, start the application, when the following information appears, it means that the application has started successfully, the default startup port is 8080. Open the browser and visit: http: / / localhost:8080 / swagger-ui.html to enter the swagger interface document interface. Finally, expand the hello interface of hello-controller, enter the parameters and click Execute, you can see the interface test results.

[0052] In summary, this method integrates the Swagger interface document, which can be used to manage and test interface problems for easy debugging, making it more suitable for user groups and eliminating the trouble of users using multiple systems. In addition, the system interface is beautified and optimized for users to better fit their usage habits and experience, providing users with a simple operating environment.

[0053] Please refer to Figure 5 The embodiment of the present invention provides a schedule management system design device based on a distributed platform, the device comprising:

[0054] Building module 500, used to establish an initial schedule management system based on JAVA language according to the SpringBoot framework;

[0055] Management module 502, used for using Nginx server to perform service proxy and load balancing on the initial schedule management platform;

[0056] The debugging module 504 is used to use the Swagger interface document to perform interface debugging on the initial schedule management system to obtain the final schedule management system.

[0057] In an embodiment of the present invention, the SpringBoot framework includes a dao layer, a service layer, a controller layer and an html layer, wherein: the dao layer is used to assist in removing data from a database; the controller layer is a business layer and a view layer responsible for developing an html interface; the controller layer is used to pass data from the service layer to an html page, and then carry the data to the html page to be jumped to.

[0058] In the embodiment of the present invention, when the management module 502 uses the Nginx server to perform service proxy for the initial schedule management platform, it is specifically used to perform the following operations: start the Nginx server to read the configuration file of the initial schedule management system, and write user information into the configuration file; define the request class according to user needs, and use the server to execute the corresponding type of data request according to the read request information to obtain the basic framework of the service proxy.

[0059] In the embodiment of the present invention, the user needs include user registration and login requests, schedule addition, deletion, modification and query requests, personal diary addition, deletion, modification and query requests, anniversary addition, deletion, modification and query requests, recycle bin restore and deletion requests and user logout requests.

[0060] In the embodiment of the present invention, when the management module 502 uses the Nginx server to load balance the initial schedule management platform, it is specifically used to perform the following operations: use Java to write a load balancer for listening to requests on a specified port and forwarding the requests to the server; configure the address and port of the server in the http part, and configure the backend service address of the load balancer in the server part; access the address of the Nginx server through a browser, refresh the browser page multiple times and observe the log output of the load balancer, and when the output result meets the preset conditions, determine that the load balancing is successful.

[0061] In the embodiment of the present invention, when the debugging module 504 uses the Swagger interface document to perform interface debugging on the initial schedule management system to obtain the final schedule management system, it is specifically used to perform the following operations: import the pre-built Swagger interface document into the initial schedule management system and enter the interface of the Swagger interface document; input parameters into the test interface of the preset controller in the Swagger interface document, and debug the initial schedule management system according to the output results to obtain the final schedule management system.

[0062] It should be noted that the schedule management system design device based on a distributed platform provided in the above embodiment is only illustrated by the division of the above functional modules. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the schedule management system design device based on a distributed platform provided in the above embodiment and the schedule management system design method embodiment based on a distributed platform belong to the same concept. The specific implementation process is detailed in the method embodiment and will not be repeated here.

[0063] The embodiment of the present application also provides a computer device, please refer to Figure 6 The computer device includes a processor and a memory, in which at least one instruction, at least one program, a code set or an instruction set is stored, and the at least one instruction, at least one program, a code set or an instruction set is loaded and executed by the processor to implement the distributed platform-based schedule management system design method provided by the above-mentioned method embodiments.

[0064] An embodiment of the present application also provides a computer-readable storage medium, on which is stored at least one instruction, at least one program, code set or instruction set, and the at least one instruction, at least one program, code set or instruction set is loaded and executed by a processor to implement the distributed platform-based schedule management system design method provided by the above-mentioned method embodiments.

[0065] An embodiment of the present application also provides a computer program product, which includes a computer program. A processor of a computer device reads the computer program from a computer-readable storage medium, and the processor executes the computer program, so that the computer device executes the distributed platform-based schedule management system design method described in any of the above embodiments.

[0066] For the convenience of description, the above system or device is described by dividing it into various modules or units according to its functions. Of course, when implementing the present application, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0067] It can be known from the description of the above implementation methods that those skilled in the art can clearly understand that the present application can be implemented by means of software plus a necessary general hardware platform. Based on such an understanding, the technical solution of the present application can be essentially or partly contributed to the prior art in the form of a software product, which can be stored in a storage medium such as ROM / RAM, a magnetic disk, an optical disk, etc., and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in the various embodiments of the present application or certain parts of the embodiments.

[0068] Finally, it should be noted that, in this article, relational terms such as first, second, third and fourth are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the statement "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0069] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A method for designing a schedule management system based on a distributed platform, characterized in that: The method comprises: Establish an initial schedule management system based on JAVA language according to the SpringBoot framework; Using Nginx server to perform service proxy and load balancing on the initial schedule management platform; The initial schedule management system is debugged using the Swagger interface document to obtain the final schedule management system.

2. The method according to claim 1, characterized in that The SpringBoot framework includes dao layer, service layer, controller layer and html layer, among which: The dao layer is used to assist in removing data from the database; The controller layer is the business layer and the view layer responsible for HTML interface development; the controller layer is used to pass the data obtained from the service layer to the HTML page, and then carry the data to the HTML page to be jumped.

3. The method according to claim 1, characterized in that: The using of the Nginx server to act as a service agent for the initial schedule management platform includes: Start the Nginx server to read the configuration file of the initial schedule management system, and write the user information into the configuration file; The request class is defined according to the user's needs, and the server is used to execute the corresponding type of data request according to the read request information to obtain the basic framework of the service agent.

4. The method according to claim 3, characterized in that The user needs include user registration and login requests, schedule addition, deletion, modification and query requests, personal diary addition, deletion, modification and query requests, anniversary addition, deletion, modification and query requests, recycle bin recovery and deletion requests and user logout requests.

5. The method according to claim 1, characterized in that The method of using the Nginx server to load balance the initial schedule management platform includes: A load balancer is written in Java to listen to requests on a specified port and forward the requests to the server; Configure the server address and port in the http section, and configure the backend service address of the load balancer in the server section; Access the address of the Nginx server through a browser, refresh the browser page multiple times while observing the log output of the load balancer, and determine that the load balancing is successful when the output result meets the preset conditions.

6. The method according to claim 1, characterized in that The initial schedule management system is debugged by using the Swagger interface document to obtain the final schedule management system, including: Import the pre-built Swagger interface document into the initial schedule management system and enter the interface of the Swagger interface document; The parameters are input into the test interface of the preset controller in the Swagger interface document, and the initial schedule management system is debugged according to the output results to obtain the final schedule management system.

7. A schedule management system design device based on a distributed platform, characterized in that: The device comprises: Building module, used to build the initial schedule management system based on JAVA language according to SpringBoot framework; A management module, used for performing service proxy and load balancing on the initial schedule management platform by using an Nginx server; The debugging module is used to use the Swagger interface document to perform interface debugging on the initial schedule management system to obtain the final schedule management system.

8. A computer device, characterized in that: The computer device includes a memory and a processor, the memory is used to store a computer program, and the processor is used to execute the computer program stored in the memory to implement the steps of any one of the methods described in claims 1-6.

9. A computer-readable storage medium, characterized in that: The storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the method described in any one of claims 1 to 6 are implemented.

10. A computer program product, characterized in that The method comprises a computer program, wherein when the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images