Four steps to complete cloud application integration

For cloud applications, it can be implemented in a variety of ways to integrate is a very salient feature of . However, each of his integration methods cannot be completely released, for to ensure the smooth deployment of the integration operation. you need to know and understand them enough.

Cloud computing market is now a mixed bag, many manufacturers continue to claim that its products are based on the cloud, but what is the cloud application, but can not say why. when most cloud applications present themselves as Web services, even if they do not comply with all the SOA protocols, they still tend to adopt an SOA architecture. With the right tool set and development attitude, you can integrate cloud applications with a variety of techniques. Of course, every integration has its limitations, and you have to be aware of it so that things can be done quickly and correctly. Now let's take a look at the four steps of cloud application integration.

Layer 1th: Screen integration

This integration method is also called aggregation (mashups) elsewhere. This method is very fast, but it is not authentic. The coding here is actually the iframes for building screen layouts, and a lot of URL with parameters that can be used to crawl things in other clouds. This is a starting way to grab images, maps, news items, and data feeds from open services like Google and Yahoo.

This approach will become more and more powerful as graphics packages and other document services become increasingly common cloud services. Ajax allows you to add a stylish, intuitive, and responsive user interface to your Web page. Unfortunately, however, aggregation does not provide better security in nature, so for sensitive data, you must also look for more ingenious programming practices to gain server-side legitimacy. You may need a single sign-on or other authentication infrastructure to control user access. So the tradeoff at this level is simple coding and read-only coding, or a very complex code to secure it.

Layer 2nd: Presentation Layer Integration

This approach is related to the way your cloud applications generate Web pages, and you may need to build a programming layer on the server side to provide a fertile ground for cloud application integration. In contrast, the aggregation method is almost entirely in the browser. Although aggregation methods are good at sticking all the paragraphs of an entire page together (such as adding a map or picture), but the presentation layer is integrated, the salient feature is the ability to add individual fields to a paragraph in a page. For example, you can add a text to the sum field of the CRM billing page by using this method: "The customer is overdue and has to pay compensation." "However, such a domain is only available in the financial system."

Of course, the advantage of this approach is also its shortcoming, that is, payment delay indicator can not be stored in the CRM system, so it can not be used to support reports, alerts, or other functions. This method is typically used only for read-only data, because the presentation layer may not have the security infrastructure used elsewhere in the system. It all depends on the language you are using and the Web security library available, but it is often not feasible to take advantage of complex security mechanisms at the presentation level.

Layer 3rd: Business logic Integration

This layer is where you can do a lot of integration because it retains the application environment and the best security and Web services infrastructure. What really makes cloud application integration unique is that this layer provides a rich and Easy-to-use API that supports paging and paging, Wsdl/soap, RESTful APIs, or simply with XML, JSON sessions. For productivity, accurate documentation and code samples are irreplaceable. Therefore, users need to evaluate cloud vendors on this basis.

Most integration architectures for cloud applications are fairly loosely coupled and are based on a request/response model. Regular polling is not a good idea, and it is difficult to establish a compact integrated loop. In situations where the cloud must push messages, the developer should create a logical relationship in the application that triggers the sending of the message. Developers also need to develop a strategy (perhaps a dedicated integration server) to handle network failures and apply downtime to ensure that messages are sent. In addition, in this layer, integrated coding will access all system objects and functions, so security is critical.

Layer 4th: Data integration

This layer will directly handle the database of cloud applications. Because the write operation is not safe enough, many cloud systems cannot really achieve the level of direct access. While direct reading of an integrated database may also cause problems, there is no indication of application status or transaction coordination in the table. But for a large amount of data to read, nothing is faster than accessing the database directly.

At this level, security is indeed a problem. Because the applied security model goes beyond the access control visibility of the table. In most cases, data integration work will have superuser privileges, so the resulting data should not be directly accessible to standard users.

"Edit Recommendation"

Year-End inventory: Cloud Application Pull the traditional software to SaaS trend is becoming more and more forced for small and medium-sized enterprises to stimulate more public cloud application migration should be prudent! Security issues and considerations for cloud Applications Cloud computing era services into enterprise informatization Fundamental cloud computing market: Who is the winner? The thinking leader of cloud computing: The application of cloud computing in Science "editor: Xin Wei TEL: (010) 68476606"