SAAS topic (iii)-implementation risks of SAAS

Describe in detail the implementation risks of SAAS (software-as-a-service.

First, the credit of software hosting services is directly related to the capabilities and investment of hosting service providers. For example, to implement online hosting of an ERP system, service providers must ensure a connection rate of more than 99.9%, software developers with the advantages of software development have to enter the network and server maintenance field, and invest a lot of money to buy servers and bandwidth. Malicious competitors may also use DDoS to attack and host services, therefore, it is necessary to invest money to purchase efficient hardware firewalls. The costs of the customer's own purchase should have been transferred to the software developers. In this way, a software developer must launch software development, network maintenance is required, and the costs have obviously increased. Large foreign software service providers such as SAP certainly have the ability to do so, but domestic software developers also do the same, will undoubtedly repeat the dust of ASP failure.

Core point of view: software developers should focus on the improvement and development of software functions. For online hosting services, they need to invest a lot of money and human resources and do what they can.

Second, I know that the B/S technology is indeed developing for the differences in software functions. Small ActiveX can complete some small functions. For the development technology EJB popular in large ERP, you can also use a Java client application to implement a GUI on the web interface. After automatically downloading the Java client package through a browser, You can implement a user interface that is the same as a traditional GUI, with a small amount of development. This method of fat client is obviously only used to deploy such applications on the LAN and on the Internet, which may be difficult for users to accept, the large Java client package downloaded before use is obviously not a friendly web access method. To develop web applications that meet the characteristics of the Internet, the current technology is not mature. To build a GUI similar to that of the GUI client, a huge amount of development work is required. Obviously, before you invest in such development, you need to consider whether it is worthwhile to do so. Whether the customer accepts the product even if it has been developed.

Core point of view: software developers should consider development costs and focus their main energy and development power on customers' acceptable solutions. Rashly innovation poses certain risks.

Therefore, for the current SaaS (software-as-a-service, software as a service), I think its prospects are the same as those of the previous ASP, traditional software developers are facing risks and challenges. Software developers without strength should not rush into this field.