Ajax joins hands with SOA to build enterprise-level applications

The rich enterprise-level application products that are effectively combined with Ajax and SOA can directly empower end users and give them powerful functions. The reason for this is that REA (rich enterprise applications) applications will be more associated with potential important users, enhancing internal rationality of users, this will also put a considerable amount of pressure on the user base in the current IT environment, thus contributing to its implementation.

Today, enterprises are trying to improve their production efficiency, and they are also exploring the restructuring of IT assets. With the help of Service-Oriented Architecture (SOA) technology, IT organizations have achieved certain results in overcoming these problems, SOA and Ajax mean a huge return for the entire IT business because of the emergence of the two. At the same time, combining these two advanced technologies is also a key application that will surely be experienced by IT business development. A brand-new network-based application called Rich Enterprise Applications or REAs.

REA not only demonstrates the technical advantages of Ajax and SOA, but also provides an advanced platform on which end users are authorized to interact and integrate, this application method is unprecedented to effectively improve product production efficiency.

Ajax provides a Rich Internet application (RIA) based on the browser. It describes a new interactive Rich application running in the browser. The RIA application is not only Ajax technology, but also other technologies such as Flex, Flash, Java, and Microsoft's XAML. From the perspective of existing enterprise applications, in terms of technical standards and adoption rate, Ajax will continuously become the key choice of Enterprise RIA application technology. Because of this, most of the discussions on RIA applications in this article will be focused on Ajax.

Compared with RIA applications, SOA is not a set of technologies, but focuses more on an architectural style or based on the principles of loose coupling, the architecture system that connects application software together by unifying standard "services" rather than hard-wired. Although we often talk about services and SOA in the same context, they are actually different. In this REA Application Discussion, the SOA Service emphasizes the loose coupling feature, but the technical content used by an SOA service is not involved. The SOA service can be an RSS source, XML presented by a database to an HTTP interface, or even a formal SOAP interface provided by a third-party search engine.

The combination of Ajax and SOA is equivalent to enriching enterprise-level applications.

The rich enterprise-level application products that are effectively combined with Ajax and SOA can directly empower end users and give them powerful functions. The reason for this is that the REA application will be more associated with potential important users, enhancing internal rationality of users, this will also put a considerable amount of pressure on the user base in the current IT environment, thus contributing to its implementation.

For this reason, the REA application will have a significant impact on the future enterprise architecture planning and design. In fact, the impact of REA applications can be found in some enterprises. Especially for some large enterprises that have implemented SOA in the early stage, such applications are already playing a role.

Early implementation enterprises have completed one or two or more SOA-related projects targeting the "Application-to-Application Integration" requirement, however, they have not completely granted these recently completed data assets to their end service users. As we all know, for most industries, the decision on income is mostly in the hands of these end users. All the support for SOA for end users and Ajax has not been taken into account in the past SOA application projects, that is, to provide users with the "Last step" business functions.

Enterprise benefits brought by REA

There are already many successful cases of world-class REA applications to share under the current development situation. Combining these examples can help explain the use of REA applications in enterprise architecture planning and design, benefits and significant impacts. Currently, we can see that the most mature REA application execution is the Ajax-based "webtop" project adopted by the Defense intelligence Analysis Institute. Each analyst starts from a blank webtop and creates a set of information resources based on the SOA service for use.

A service may consist of scheduled and expected events, such as fact and statistics provided or reflected by some archival databases or third-party news services. Many available services are SOA-oriented services that can be directly used for service architecture systems extracted from existing integrated data resources. Other services come from "virtualization" services that are not fully formal resources. These resources can be databases or EJB applications, it can be a "service mashups" composed of two or more small-granularity resources. These hybrid services are more useful for analysts than those small-granularity individual resources.

Once the service is selected, it will be personalized in a variety of ways. For example, you can apply a filter to change or format the display area ...... Even some of your expected-level applications, specific data records or projects can also be used by other users within a community through the social form of sharing. For example, an analyst can create a valid data item on webtop and display it to other analysts. Many services also allow you to update the original resources while updating the data. At the same time, they will instantly reflect the synchronous display of each data on them through webtop.

Quick implementation of REA applications

Does the preceding example show the quick implementation examples provided by the REA application? First, we need to know that users are in the position of a driver who holds the steering wheel of this exceptionally powerful "transport. This REA application of user authority is equally feasible for employees in various industries, such as medical case card management personnel, sales representatives, call center staff, credit analysts or claims management personnel.

Secondly, in this REA application example (almost all REA applications do), Ajax and SOA are closely linked. It is difficult to determine whether it is because of SOA. If Ajax is introduced, or if Ajax is used, the SOA will be further integrated into the enterprise's architecture plan. Perhaps this also depends on the enterprise's own advantages and the implementation time curve arrangement, through Ajax and SOA to expand the specific application. It can be determined that the effective combination of the two technologies will produce greater utility than the independent use of any technology.

Also, do not mistakenly think that the REA application only targets portals. Otherwise, the REA application should be considered as a portal without traditional portal services. The current Portal is a single entry point for enterprise information, and it has become a place where too much information is collected. The REA application is displayed as a portal. On the other hand, it not only enables users to find the information they are willing to search, it is more able to combine irrelevant information data and give users a personalized perspective-this is a brand new integrated application driven by the user's own consciousness. When users share these specific tiny integrations, they are essentially creating a "Long Tail" of the integration effect.

How does the REA application fill the user-driven gap in the IT business?

However, as you may have realized, in the current typical enterprise architecture, there are some components that can be used to support REA applications, but these components are lost in traditional applications. Appropriate service granularity is still an artistic form in the entire enterprise architecture application. Pushing data to browser-based applications is not common, but the "virtualization" service and "hybrid service" are even more unknown.

All these communications must be implemented securely in accordance with the available service policies determined by the underlying services. This is also an elegant metric for user groups at all levels.

We must never ignore that most enterprises do not have their own enterprise-level Ajax development teams. Most of them are waiting for SOA projects to take effect in production. They need some tools that support visual development, some debugging tools, and some code reuse tools that are developed in a "table and button" window from the IDE. IDE also helps them create some lightweight code and optimize the execution in the browser.

There are also some small but equally important issues, such as how to solve the browser compatibility issues of portal websites, multi-language support problems, the issue of easy website guidance on webpages, and the issue of coexistence policies.

The above is why Ajax and SOA, of course, you can also name them as the reason why REA applications may have a huge impact on future Enterprise Architecture Planning and Design, as described in this article. From the end-user requirements of REA application features in IT businesses, we can clearly see that the new-generation enterprise architecture will inevitably take user-driven as the premise. In the next few years, most of the business applications will serve as the basis for REA applications, and the IT department is responsible for arranging plans for this demand.

1. Ajax advantages in enterprise applications
2. Analysis on the ten reasons for using AJAX
3. How to Implement the most basic AJAX framework