Interface method suitable for SaaS software

Abstract

The invention relates to an interface method suitable for Software as a Service (SaaS) software, which is characterized by comprising the following steps of: firstly, coding messages related to the SaaS software in a uniform message format; secondly, deserializing the messages by means of a uniform interface processing logic to form specific internal message objects; next, calling different operation processing logics to process the message objects so that the external release forms of the messages are unrelated to the specific processing logics of the messages; then fully decoupling the external release forms of the messages from the specific processing logics of the messages in a factory pattern; and finally, when a new external interface interaction way is needed to be added, adding a logic of obtaining the messages associated with the interaction way, thereby establishing an interface. In this way, through the design and establishment of a uniform message standard, the external interface of a SaaS software access component can be standardized so that lots of operations can be all processed by means of the same interface; and for an independent software provider, the technical difficulty is reduced and the release workload is also reduced.

Description

technical field [0001] The invention relates to an interface method, in particular to an interface method suitable for SaaS software. Background technique [0002] With the rapid development of the Internet, the demand for providing software as a form of service to customers is gradually increasing, and the emergence of the new model of SaaS is exactly in line with this demand. SaaS is a software architecture with the goal of "software deployment as a hosting service, which can be directly accessed through the network, can be customized by customers, and is easy for developers to implement". It is a business model that provides convenient, fast, stable and reliable, low-cost, low-risk, high-security, professional and flexible, and various types of software enterprise-level information services for the majority of small and medium-sized enterprises. [0003] Just as the characteristics of the SaaS operation model described above, a successful SaaS service requires the partic...

AI Technical Summary

Problems solved by technology

Moreover, the current interface implementation method is still one interface method and one URL. There is a great coupling between the interface methods, and because the parameters are included in the URL, there are also certain security issues.

[0012] Secondly, from the perspective of message specification, the defects and problems of the existing SaaS software access component interface are explained: most of the SaaS software access components currently have one function and one interface. Whether it is the HTTP Post method, there will be a specified WebMethod or URL corresponding to it. If you want to add an interface, you must add the code of the corresponding interface, which will affect the original interface that does not need to be changed, and it will also be the same for ISV SaaS software products In this case, even the callers who do not need to generate the corresponding interface need to change the code

This will have a major impact on the stability and scope of the interface system

Images