WO2015062399A1

WO2015062399A1 - Cloud service platform middleware and cloud uploading method

Info

Publication number: WO2015062399A1
Application number: PCT/CN2014/088289
Authority: WO
Inventors: 张清柱
Original assignee: 乐视网信息技术（北京）股份有限公司
Priority date: 2013-10-31
Filing date: 2014-10-10
Publication date: 2015-05-07
Also published as: CN103533087A

Abstract

Provided in the present invention are a cloud service platform middleware and a cloud uploading method. The middleware comprises a core engine layer, a data layer, a support layer and a message component layer, wherein the core engine layer is used for providing interfaces for calling different cloud services in order that the interfaces are called by a cloud application layer outside the middleware; the data layer is in communication with the core engine layer and used for saving the cloud data of users; the support layer is in communication with the core engine layer and used for providing service components for realizing different cloud services; the message component layer is in communication with the support layer and the core engine layer respectively and used for message transfer between the support layer and the core engine layer. In this way, the development time of cloud applications can be greatly shortened, and the development cost can be reduced. In addition, the user data under different cloud applications can be integrated through the middleware on the basis of the cloud applications set up by the middleware of the present invention, thereby achieving data being got through and sharing among different cloud applications and also saving storage resource and improving user experience.

Description

Cloud service platform middleware and cloud uploading method

This application claims priority to Chinese Patent Application No. 201310533857.5, entitled "A Cloud Service Platform Middleware and Cloud Upload Method", filed on October 31, 2013, the entire contents of which are incorporated by reference. In this application.

Technical field

The present invention relates to the field of communications technologies, and in particular, to a cloud service platform middleware and a cloud uploading method.

Background technique

With the continuous development of computer technology, cloud services have been widely accepted and used by their reliability and versatility. Immediately, more and more cloud applications have emerged to meet people's different needs, such as cloud photo albums, cloud network disks, and cloud video. , cloud notes and more.

At present, when a cloud service provider builds a cloud application service platform, most of them are customized cloud application construction by analyzing user usage scenarios. If the cloud service is to be enhanced based on the original cloud application, the original cloud needs to be overthrown. The service platform of the application is rebuilt; or one or more parallel cloud application service platforms are built on the basis of the original cloud application service platform. For the first method, it takes a long time and costs a lot. In the second method, the cloud applications are relatively independent, and the cloud data sharing of the same user cannot be realized between the cloud applications. The following is an example.

For example, on the basis of a personal cloud video-based service platform, a cloud application of a personal cloud album is launched, which corresponds to two methods of the prior art, and the specific implementation can be embodied as:

In the first way, the architecture of the existing cloud video application platform is overturned, the current usage scenario is re-analyzed, and a new system architecture is constructed to support the two usage scenarios of cloud video and cloud album. This approach obviously costs a lot of money, especially when the user needs to update the usage scene more frequently, which is more expensive.

Method 2: Independently consider the cloud photo album application, that is, analyze only the use scene of the cloud photo album, customize an independent service platform for it, and independently build a network infrastructure that conforms to the characteristics of the cloud photo album application, thereby providing cloud video to the user. , the comprehensive use of cloud albums. In this way, the user data of the two cloud applications are independent and cannot be opened. That is to say, the cloud data (such as the user's underlying data, business data, etc.) of the user in the cloud video application cannot be shared into the cloud photo album application. . In this way, the two service platforms may need to maintain a large amount of the same data, resulting in waste of storage resources; for the user, the user experience may also be reduced.

Summary of the invention

The cloud service platform middleware and the cloud uploading method of the embodiment of the invention are used to solve the problem that the prior art has the cost and the data cannot be opened when the cloud service is enhanced.

To this end, the embodiments of the present invention provide the following technical solutions:

A cloud service platform middleware, the middleware includes a core engine layer, a data layer, a support layer, and a message component layer, wherein

The core engine layer is configured to provide a calling interface of different cloud services, and is invoked by a cloud application layer outside the middleware;

The data layer communicates with the core engine layer to save user cloud data;

The support layer is in communication with the core engine layer for providing service components for implementing different cloud services;

The message component layer communicates with the support layer and the core engine layer, respectively, for implementing message transfer between the support layer and the core engine layer.

Preferably, the service component provided by the support layer comprises at least one of the following service components:

Image thumbnail component, static resource pool, video transcoding system, file distribution and acceleration system, distributed file storage system.

Preferably, the middleware further includes a data cache layer.

The data cache layer is configured to cache user cloud data that meets a preset rule in the data layer.

Preferably, the core engine layer is further configured to integrate cloud data of the same user in different cloud services, and save the correspondence between the user and the integrated cloud data.

Preferably, the core engine layer is further configured to monitor user access to different cloud services, and generate cloud logs to save to the data layer.

Preferably, the message component layer is further configured to communicate with the cloud application layer to implement message delivery between different cloud services.

Correspondingly, the embodiment of the present invention further provides a cloud uploading method, where a developer constructs an application layer that can provide a cloud uploading service, and causes the application layer to communicate with the cloud service platform middleware, and performs cloud uploading according to the following steps:

Sending, by the application layer, a call interface of a cloud upload service in a core engine layer of the middleware a file upload request, the request including a file fingerprint of the file to be uploaded;

The cloud uploading service determines, according to the file fingerprint, whether the file to be uploaded has been uploaded;

If the upload is not completed, notifying the application layer to upload the file to be uploaded to the distributed file storage system in the support layer of the middleware;

After the file is uploaded, the distributed file storage system writes the storage address of the file into the message queue of the message component layer of the middleware, and feeds back the information of the file upload success to the application layer;

The message reading process maintained by the core engine layer accesses the message component layer at a preset interval, reads a file storage address written by the distributed file storage system, and saves the file storage address to the The data layer of the middleware.

Preferably, if the file to be uploaded is a picture, the method further includes:

After the file is uploaded, the distributed file storage system generates a thumbnail using the picture thumbnail component and stores the thumbnail in a static resource pool.

Preferably, if the file to be uploaded is a video file, the method further includes:

After the message reading process reads the file storage address from the message component layer, the core engine layer controls the video transcoding system of the support layer to read the read from the distributed file storage system. Video files and video transcoding;

After the transcoding is completed, the video transcoding system saves the transcoded file to the file distribution and acceleration system of the support layer, and writes the storage address of the transcoded file to the message queue of the message component layer. in;

The message reading process accesses the message component layer according to a preset interval, reads a storage address of the transcoded file from the storage address, and saves the data to the data layer.

Preferably, the file to be uploaded request further includes a callback address, and the method further includes:

After saving the file storage address to the data layer of the middleware,

The cloud uploading service sends an upload success confirmation message to the application layer by using the callback address.

The cloud service platform middleware and the cloud uploading method in the embodiment of the present invention, the middleware manages and maintains the underlying services and data of multiple cloud services in a unified manner, and the developer only needs to construct a simple application layer, and then invokes the middleware to provide External interface can build a new cloud application, so you can greatly shrink The development time of short cloud applications reduces development costs. In addition, based on the cloud application built by the middleware of the present invention, the data of the user under different cloud applications can be integrated through the middleware to realize data opening and sharing between different cloud applications, thereby saving storage resources and improving user experience. .

DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the description of the prior art will be briefly described below. Obviously, the drawings in the following description are only It is a certain embodiment of the present invention, and other drawings can be obtained from those skilled in the art without any creative work.

1 is a schematic diagram of a cloud service platform middleware according to an embodiment of the present invention;

2 is a flowchart of Embodiment 1 of a cloud uploading method according to an embodiment of the present invention;

FIG. 3 is a flowchart of Embodiment 2 of a cloud uploading method according to an embodiment of the present invention.

detailed description

The embodiments of the present invention are further described in detail below with reference to the accompanying drawings and embodiments.

In order to solve the problem that the prior art is to enhance the cloud service based on the original cloud application, the new cloud application service platform is time-consuming and costly, and the embodiment of the present invention provides a cloud service platform middleware, which is provided for the developer. Technical support for multiple cloud applications. In this way, when it is necessary to incubate a new cloud application, the developer only needs to construct an application layer, and then invokes the middleware of the embodiment of the present invention through the application layer, and implements a new cloud application by means of splicing the application layer and the middleware. . Compared with the prior art, it takes 3 to 5 months to construct a new cloud application. After adopting the solution of the invention, it takes only 1 to 2 months to complete, which greatly shortens the development time and reduces the time cost. .

It should be noted that the application layer can be understood as a user interaction interface of the cloud application, that is, a user-visible and directly operable interface, which faces different cloud service requirements of the user, and can implement clients such as a mobile terminal, a PC terminal, and a TV terminal. The cloud application show.

The configuration of the cloud service platform middleware of the embodiment of the present invention is explained below.

Example 1

Referring to FIG. 1 , a schematic diagram of a cloud service platform middleware according to an embodiment of the present invention is shown. As an embodiment 1 of a middleware component of the embodiment of the present invention, the middleware may include a core engine layer, a data layer, a support layer, and a message component. Floor. The layers are explained below.

(1) The core engine layer is used to provide a call interface of different cloud services for the cloud application layer call outside the middleware.

The most basic function of the core engine layer is to maintain the calling interface for different cloud application services. Referring to the example in Figure 1, the core engine layer can provide uploading, downloading, moving, renaming, searching and other services to the application layer. Developers provide a call interface to these services for their use. In this way, when the developer intends to build a new cloud application, it is only necessary to develop an application layer that implements the business presentation, and call the corresponding interface provided by the core engine layer when needed.

It should be noted that the core engine layer, as the external interface of the middleware of the present invention, can directly communicate with the application layer, and establish communication with the data layer, the support layer, or the message component layer according to actual usage, which will be described below. An explanation is given.

(2) The data layer communicates with the core engine layer to store user cloud data.

The most basic function of the data layer is to implement cloud storage, which is mainly formed by database components.

(3) The support layer communicates with the core engine layer to provide service components that implement different cloud services.

After the application layer invokes the core engine layer, the core engine layer cooperates with the support layer to implement the cloud service according to different cloud services provided by the application layer for the user. Referring to the example illustrated in FIG. 1, the support layer may be embodied as: a picture thumbnail component, a static resource pool, a video transcoding system, a file distribution and acceleration system, a distributed file storage system, a monitoring system, and the like.

The components included in the support layer can be divided into common components for implementing different cloud services. For example, files uploaded by the cloud disk disk service and the cloud photo album service can be saved to the distributed file storage system. For the two cloud applications, A distributed file storage system can be considered a generic component. Alternatively, different cloud services can monitor the health status of application interfaces, message queues, servers, networks, disks, database masters and slaves through monitoring systems, so the monitoring system can also be regarded as a common component.

In addition, the components of the support layer can also be divided into personalized components for implementing personalized cloud services. For example, for the cloud photo album service, in addition to saving the user-uploaded album through the distributed file storage system, the user is detected. When the uploaded file is an image, the image thumbnail component is used to process the image to generate a thumbnail and push it into the static resource pool to improve the image access speed. Again For example, for a video file, it may be shot by a different terminal such as a mobile phone or a video camera, or may have a different video format. In order to ensure that the user successfully uploads the video file through any device, the video should be played in any place. The file is uniformly transcoded. Image thumbnail components, static resource pools, video transcoding systems, etc. can all be considered as personalized components.

(4) The message component layer communicates with the support layer and the core engine layer, respectively, for implementing message transmission between the support layer and the core engine layer.

The most basic function of the message component layer is to implement the message transfer from the support layer to the core engine layer. For example, when the application layer calls the core engine layer to provide an upload service to the user, the core engine layer cooperates with the distributed file storage system of the support layer to perform file uploading and storage; after the upload is completed, the distributed file storage system also needs to store the address. Save to the data layer, so that when the user needs to download the file, the core engine layer can read the file storage address from the data layer, and then go to the corresponding location to get the file. In this process, the support layer passes the storage address to the core engine layer through the message component layer, which is then saved to the data layer by the core engine layer, which will be explained in the cloud upload method below.

In this way, the developer can quickly and conveniently construct a new cloud application by using the middleware provided by the embodiment of the present invention, and in the development process, the developer only needs to construct a simple application layer, and then make the application layer and the middleware. You can interact with the external interface. The underlying services and data for implementing cloud services can be managed and maintained by middleware, which can greatly reduce unnecessary repetitive development work and reduce the cost of data synchronization, software and hardware development, maintenance and upgrade.

Example 2

In addition, in the prior art, the cloud service mode 2 is enhanced, and the data between the two independent service platforms cannot be opened. The embodiment of the present invention further provides the second embodiment of the middleware component. In this embodiment, the core engine layer is also used to integrate the cloud data of the same user in different cloud services, and save the correspondence between the user and the integrated cloud data.

That is to say, the developer can construct an application layer of a plurality of different cloud services, and use the middleware of the present invention to splicing out a plurality of different cloud applications, such as a cloud network disk, a cloud album, a cloud backup, and the like as shown in FIG. The application layer of the application. In order to ensure that users do not use the cloud application to open and share data, the core cited The engine layer should also have the ability to integrate user cloud data.

The specific process may be embodied as: when the user uploads the cloud application by using the middleware built by the present invention, the core engine layer establishes a correspondence between the user identity information and the cloud application, because the cloud application and the user data also correspond to each other. Therefore, the correspondence between the user identity information and the user data is established, so that when the user needs to implement the linkage of the related cloud service, the core engine layer can find the required data feedback to the user according to the conditions input by the user, It saves storage resources and improves user experience. The process is illustrated below.

For example, the cloud media disk and the cloud photo album are implemented by the middleware of the present invention. To realize the display and management of the personal photos of the cloud network disk in the cloud photo album, the process can be embodied as follows: First, the core engine layer is established. The mapping relationship between the user identity code and the cloud network disk, thereby realizing the association between the user and all user data of the cloud network disk (including, of course, the association between the user and the personal photo); correspondingly, the core engine layer also establishes the name The mapping relationship between the user's identity code and the cloud album realizes its association with all the user data of the cloud album. Thus, the user and its association relationship between the two cloud applications are established. Secondly, when the user wants to realize the display of the personal photos of the cloud network disk to the cloud album, the core engine layer will determine whether the user has a mapping relationship with the cloud network disk according to the condition. If there is any, you can find and read the personal photos that the user needs from the cloud network disk, and share them to the cloud photo album to realize the personal photos in the cloud network disk in the cloud photo album.

Example 3

After the data is opened and shared between the different cloud applications, in order to realize the data communication between the underlying systems of different cloud applications, and reduce the coupling and the loose coupling between the systems, the embodiment of the present invention also provides the third embodiment of the middleware composition scheme. . In this embodiment, the message component layer is further configured to communicate with the cloud application layer to implement message delivery between different cloud services.

That is to say, the message component layer in the present invention can implement message delivery between different applications in addition to message delivery under the same application. The following is an explanation of the example of passing shared information.

The message delivery in the same application can be embodied as: user A shares a photo with user B in the cloud photo album application, and the message component layer sends a sharing information reminder to user B in the cloud photo album application, prompting user B to have a user currently. A shared a photo with him.

The message passing in different applications can be embodied as: User A shares with User B in the cloud photo album application. A photo, because the data between different applications is opened, the message component layer can also send a sharing information reminder to the user B in the cloud network disk application, prompting the user B that the user A currently shares the user A in the cloud photo album application. photo. As a preferred solution of the embodiment of the present invention, when the user B clicks on the link address in the shared information reminder, the user can directly jump from the cloud network disk to the cloud photo album to view the photo shared by the user A.

It should be noted that the delivery of the storage address introduced in Embodiment 1 above can be understood as an embodiment of the message delivery process under the same application.

Example 4

In order to improve the access speed of the cloud application built by the middleware of the present invention, the embodiment of the present invention further provides Embodiment 4 of the middleware composition scheme. In this embodiment, the middleware further includes a data cache layer, configured to cache user cloud data in the data layer that meets a preset rule.

In general, when a user accesses a cloud application and wants to read or download data from it, the core engine layer needs to be called through the application layer, and then the core engine layer reads the corresponding user data from the data layer according to the user's needs. In order to improve the processing speed of the process, the embodiment of the present invention further adds a data cache layer with a faster read speed, and partially meets the preset rule (the preset rule may be embodied as data commonly used by the user, or a specific type set by the user. The data of the data, etc., which is not limited by the present invention, is read from the data layer and stored in the data cache layer. When the user needs to access the data, the core engine layer first reads from the data cache layer, and if the data cache layer does not exist, accesses the data layer and reads from it.

The data cache layer may include a data cache component, a session sharing component, etc., since both the data layer and the data layer are for cloud data storage and query, so in the example shown in FIG. 1, the two are not strictly demarcated.

Example 5

In order to record the access situation of the cloud application built by the middleware of the present invention, the embodiment of the present invention further provides Embodiment 5 of the middleware composition scheme. In this embodiment, the core engine layer is further configured to monitor user access to different cloud services, and generate cloud logs to save to the data layer.

In other words, the core engine layer also has a monitoring function that can statistically analyze each cloud application. The number of users, the amount of access of the preset time period (such as daily, hourly, etc.), the usage activity of the application, etc., corresponding to this, the data layer also includes a log component for storing data monitored by the core engine layer.

The cloud uploading process is taken as an example to explain the use process of the cloud application built by the middleware of the present invention.

Example 6

As described above, from the developer's point of view, it needs to build an application layer that can provide cloud upload service, and then make the application layer communicate with the cloud service platform middleware of the present invention, and perform cloud upload according to the following steps. For details, refer to the flowchart of Embodiment 1 shown in FIG. 2, which may include:

Step 101: The application layer sends a file upload request to a call interface of a cloud upload service in a core engine layer of the middleware, where the request includes a file fingerprint of a file to be uploaded.

The application layer presents the operation interface to the user, and when receiving the file upload request sent by the user through the client, establishes communication with the core engine layer of the middleware, invokes the file upload service interface provided by the core engine layer, and uploads the file upload request. Submit to this interface to trigger the cloud upload process.

It should be noted that the file upload request mainly includes the file fingerprint of the file to be uploaded, and the file fingerprint can be regarded as the file identity information. Each file has its own unique file fingerprint, and the file fingerprint can pass the file content. File size, file type, etc. are formed.

Step 102: The cloud uploading service determines, according to the file fingerprint, whether the file to be uploaded has been uploaded. If the uploading is not completed, step 103 is performed; if the uploading is completed, the uploading is successful to the user.

After receiving the file upload request forwarded by the application layer, the cloud uploading service in the core engine layer first determines whether the file to be uploaded has been uploaded according to the file fingerprint:

If the upload has been completed (either the user has uploaded the file before, or other users have uploaded the file, it can be considered as having completed the upload. For other users who uploaded the file, the current user is equivalent to sharing the other The user's upload progress and upload file), the core engine layer directly feeds the user through the application layer to feed the file successfully, and realizes the file second transmission.

If the upload is not completed (can be embodied as a file does not exist, or the file upload is interrupted), on the cloud The delivery service will look up the upload node closest to the user client and assign the upload node to the client for file upload.

Step 103: The application layer is notified to upload the file to be uploaded to a distributed file storage system in a support layer of the middleware.

This step is to find the address of the uploading node that is closest to the client, and then notify the client of the address of the uploading node through the application layer, and then upload the file to be uploaded to the supporting layer of the middleware through the uploading node, specifically uploading to the supporting layer. Distributed file storage system.

Step 104: After the file is uploaded, the distributed file storage system writes the storage address of the file into the message queue of the message component layer of the middleware, and feeds back the information of the file upload success to the application layer.

Step 105: The message reading process maintained by the core engine layer accesses the message component layer at a preset interval, reads a file storage address written by the distributed file storage system, and saves the file storage address. To the data layer of the middleware.

After the file upload is completed, you need to save the storage address of the file to the data layer, so that the subsequent users can use it when reading or downloading the file.

In the first aspect, the distributed file storage system writes the storage address of the file (or as a storage path) to the message queue of the message component layer, and also feeds back the successful uploading of the file to the client user (mainly through the application). The layer is shown to the user for viewing).

In the second aspect, the core engine layer maintains a message reading process, which is a timed script that can access the message component layer every predetermined time interval to read the message in the message queue. After the distributed file storage system writes the file storage address to the message queue, it can be read by the message reading process and saved to the data layer. So far, the process of cloud uploading using the cloud application built by the middleware of the present invention is completed.

Example 7

Referring to FIG. 3, a flowchart of Embodiment 2 of the cloud uploading method of the present invention is shown, which may include:

Step 201: The application layer sends a file upload request to a call interface of a cloud upload service in a core engine layer of the middleware, where the request includes a callback address and a file fingerprint of the file to be uploaded.

Step 202: The cloud uploading service determines, according to the file fingerprint, whether the file to be uploaded is finished. If the upload is not completed, step 203 is performed; if the upload has been completed, the uploading is successful to the user.

Step 203: The application layer is notified to upload the file to be uploaded to a distributed file storage system in a support layer of the middleware.

Step 204: After the file is uploaded, the distributed file storage system writes the storage address of the file into the message queue of the message component layer of the middleware, and feeds back the information of the file upload success to the application layer.

Step 205: The message reading process maintained by the core engine layer accesses the message component layer at a preset interval, reads a file storage address written by the distributed file storage system, and saves the file storage address. To the data layer of the middleware.

Steps 201 to 205 are basically the same as steps 101 to 105, and are not described herein again. The difference is that the file upload request in the embodiment further includes a callback address, that is, the client user wants to feed back the upload success confirmation message through the callback address after the platform confirms that the file is successfully uploaded.

Step 206: The cloud upload service sends an upload success confirmation message to the application layer.

When the client requests stricter file uploading results, the callback address can be added to the file upload request, and the platform is required to feed back the final upload status of the file.

In the cloud uploading method embodiment 1, after the file is uploaded, the distributed file storage system feeds back the message that the file upload succeeds to the client. However, as described above, the distributed file storage system feeds back the message to the application layer. After that, the message reading process reads the storage address and saves the storage address to the data layer. No matter which of these processes is wrong, the user may not be able to read or download the upload correctly. file. Therefore, in this embodiment, the uploading result is required to be high (such as cloud backup), and the callback is used to ensure that the file storage address is correctly saved to the data layer, and the core engine layer sends a file upload success confirmation to the application layer. The message is used to enable the client user to grasp the final upload status of the file.

It should be noted that the file uploaded by the cloud may be an ordinary document, or a picture type file, or a video type file. For the picture type and the video type file, the personalization of the support layer is also needed in the uploading process. The components are specially treated and explained below.

After the file is uploaded, if the distributed file storage system determines that the file is a picture class file, The image thumbnail component is triggered to generate a thumbnail and the thumbnail is stored in a static resource pool. This process can be performed before the distributed file storage system writes the file storage address to the message queue, or after the file storage address is written to the message queue, or both actions are performed, and the present invention does not limited.

If the file to be uploaded is a video file, after the message reading process reads the storage address of the file from the message queue of the message component layer, the core engine layer sends the file storage address to the video transcoding system to control the video transfer. The code system reads the video class file from the distributed file storage system and performs video transcoding. In order to improve the reading speed of the transcoded video file, after the transcoding is completed, the video transcoding system will also save the transcoded file to the file distribution and acceleration system, and in the file distribution and acceleration system. The storage address is written to the message queue of the message component layer, waiting for the message reading process to read and save it to the data layer. That is to say, for a video file, the data layer stores two storage addresses, one is the storage address of the original uploaded file stored in the distributed file storage system for the user to view and download; one is stored in the file. The storage address of the transcoded file in the distribution and acceleration system for the user to play on different devices.

The embodiments of the present invention have been described in detail above, and the present invention has been described with reference to the specific embodiments. The description of the above embodiments is only used to help understand the method and platform of the present invention. Meanwhile, for those skilled in the art, The present invention is not limited by the scope of the present invention.

Claims

A cloud service platform middleware, wherein the middleware includes a core engine layer, a data layer, a support layer, and a message component layer, where

The core engine layer is configured to provide a calling interface of different cloud services, and is invoked by a cloud application layer outside the middleware;

The data layer communicates with the core engine layer to save user cloud data;

The support layer is in communication with the core engine layer for providing service components for implementing different cloud services;

The message component layer communicates with the support layer and the core engine layer, respectively, for implementing message transfer between the support layer and the core engine layer.
The method of claim 1, wherein the service component provided by the support layer comprises at least one of the following service components:

Image thumbnail component, static resource pool, video transcoding system, file distribution and acceleration system, distributed file storage system.
The method of claim 1 wherein said middleware further comprises a data cache layer.

The data cache layer is configured to cache user cloud data that meets a preset rule in the data layer.
The method according to any one of claims 1 to 3, characterized in that

The core engine layer is also used to integrate cloud data of the same user in different cloud services, and save the correspondence between the user and the integrated cloud data.
The method according to any one of claims 1 to 3, characterized in that

The core engine layer is further configured to monitor user access to different cloud services, and generate cloud logs to save to the data layer.
The method according to any one of claims 1 to 3, characterized in that

The message component layer is further configured to communicate with the cloud application layer to implement message delivery between different cloud services.
A cloud uploading method is characterized in that a developer constructs an application layer capable of providing a cloud uploading service, and the application layer communicates with the cloud service platform middleware according to any one of claims 1 to 6, according to the following steps: Cloud upload:

Sending, by the application layer, a file upload request to a call interface of a cloud upload service in a core engine layer of the middleware, where the request includes a file fingerprint of a file to be uploaded;

The cloud uploading service determines, according to the file fingerprint, whether the file to be uploaded has been uploaded;

If the upload is not completed, notifying the application layer to upload the file to be uploaded to the distributed file storage system in the support layer of the middleware;

After the file is uploaded, the distributed file storage system writes the storage address of the file into the message queue of the message component layer of the middleware, and feeds back the information of the file upload success to the application layer;

The message reading process maintained by the core engine layer accesses the message component layer at a preset interval, reads a file storage address written by the distributed file storage system, and saves the file storage address to the The data layer of the middleware.
The method according to claim 7, wherein if the file to be uploaded is a picture, the method further comprises:

After the file is uploaded, the distributed file storage system generates a thumbnail using the picture thumbnail component and stores the thumbnail in a static resource pool.
The method according to claim 7, wherein if the file to be uploaded is a video file, the method further comprises:

After the message reading process reads the file storage address from the message component layer, the core engine layer controls the video transcoding system of the support layer to read the read from the distributed file storage system. Video files and video transcoding;

After the transcoding is completed, the video transcoding system saves the transcoded file to the file distribution and acceleration system of the support layer, and writes the storage address of the transcoded file to the message queue of the message component layer. in;

The message reading process accesses the message component layer according to a preset interval, reads a storage address of the transcoded file from the storage address, and saves the data to the data layer.
The method according to claim 7, wherein the file to be uploaded request further includes a callback address, and the method further includes:

After saving the file storage address to the data layer of the middleware,

The cloud uploading service sends an upload success confirmation to the application layer by using the callback address interest.