Public cloud services under mixed cloud applications little common sense

We know that to achieve the most efficient mix, we should take full advantage of all the components. In the cloud computing platform, the hybrid cloud is now a buzz, and future hybrid clouds must take advantage of the new capabilities of the public cloud and keep private IT investments. If you do not consider the mixed requirements in the data at run time, the risk costs of the enterprise will rise in a straight line, benefit implementation issues, or even technology fail completely. Most users indicate that the main time the cloud project failed is in the planning phase. It is only when the project plan is properly developed that there is a good chance to achieve success.

In order to support the hybrid design of public cloud applications, there are four factors that must be considered: application models, platforms, database access, and how components are connected together.

Select Application Model

In the future of the hybrid design of public cloud applications, the key consideration is the application model, whether front-end or back-end model. The Enterprise Business section reports that their current public cloud application Two-thirds is a front-end model in which cloud technology is added to the user's current application system. This is also the most commonly used model of internet retailing applications. Most of the rest of the enterprise is concerned about cloud outbreaks or backing up the recovery applications of existing systems.

If you are developing a public cloud component for the hybrid, be sure to adjust the current architecture, adapt to the mixed local side, or adjust the existing architecture to the cloud. These are all things that you need to address in the planning phase, so you should be certified in the initial and future requirements of your application. Optimal blending is most important in controlling workflows between public and private components. You need to support the current it time, but you also need to develop the only flexible and temporary cloud properties.

Creating a harmonious relationship with a platform

The technical level of easy mixing is based on platform harmony. A hybrid cloud can theoretically support workflows through any set of interfaces that can be supported by the public cloud or private IT support. In practice, there are different operating systems and middleware in the public cloud that complicate things and become more expensive, especially in public cloud operations.

If you have a unified local IT architecture, you need to authenticate the same architecture for the cloud. If you plan a hybrid application of cloud bursts or failback, it's almost mandatory to use the same operating system and middleware in the cloud as in the data center. Even when building the front end of the class web to the current IT platform, some of the key components that might run on the public cloud, depending on performance or with the backup tuning architecture.

Let the database access the public cloud and local it

The third question to consider when designing a public cloud application for a hybrid is how you can provide the public cloud and local IT resources based on the data requirements. Store critical enterprise data to remote design cost and security issues, so most users choose to keep their databases locally. Therefore, when a mixed-application cloud component must access data, access must be connected across the WAN between the cloud and the data center, which is also expensive and performance-intensive.

A more appropriate solution for cloud bursts or failback applications is to use the Query Services database management system rather than having the cloud component access the database using standard disk I/O. For front-end applications, it may be more valuable to create a logical separation in the current database. For example, a retail cloud front-end may use a product category from a standard retail inventory application, but does not contain inventory quantity information; The user browses the static category, but only connects to the real database when the order is set.

Identify the link for the application

The final consideration is also the most technical: how do your hybrid applications connect at the application interface (API) level, and how do your applications manage context or state? In software development, components use API links, and these APIs often define how components track the processes they are trying to support.

The challenge for a mixed-swap development of public cloud applications is that most enterprise software is based on strict service-oriented architecture (SOA) and Simple Object Access Protocol (SOAP) APIs. Most cloud applications typically take rest and HTTP architectures. The difference is that SOA and SOAP link components through multiple transaction phases, and all components automatically synchronize their behavior through their APIs. With rest or HTTP, most of the time the client, the browser interface, tracks the context, which is explicitly delivered to each component through the API.

The real difference is that a copy of any software component accesses the appropriate database to handle any rest request, but the SOA-SOAP request must be processed by the specific software element that was originally selected. Rest architectures support simple sharing and load balancing, but are difficult to implement in Soa-soap. This means that any hybrid architecture that might contain cloud bursts or failback should carefully consider the rest architecture. Full-end applications can use the application components, run in the cloud or local, to bridge the cloud rest or web-friendly architecture and more traditional data center application architecture.

"Edit Recommendation"

Towards the open hybrid cloud of the thoroughfare 2014, the hybrid cloud is widely used for one year of careful cloud washing: the public cloud, the private cloud and the hybrid cloud enterprise application Cloud computing Five stages: The mixed cloud is not the endpoint "the Executive Editor: Dan TEL: (010) 68476606"