Document directory
- New SOA business language new system architecture-SOA and Web 2.0
SOA new business language new system architecture-SOA and Web 2.0 "we are increasingly aware that the concepts of Web 2.0 and SOA are largely the same, it's just being whitewashed into different parts of the software (if there are actually different )." -Dion hinchliffe zdnet colleague Dion hinchliffe has been using SOA and Web 2.0 for a while. In a new blog, he said that SOA and Web 2.0 overlap many things, such as invoke-based services, which can exist in any network location. The common characteristics of SOA and Web 2.0 are much different, and Web 2.0 plays a role in promoting SOA. Until now, SOA and Web 2.0 have different supporters-SOA involves more enterprise structures and open-up shops, while Web 2.0 focuses more on users. This difference is changing as more companies accept Web 2.0, but Dion still believes that these two technologies have different focuses: "O 'Reilly's Web 2.0 tells us that data is the most important part of today's software applications... SOA tells us that the service is the center. Data transmission services in SOA are also very important, but traditional SOA focuses more on the joint of IT systems than those that can make the joint more valuable ." Dion concluded that SOA may be a smooth pipeline, but it is not the value of water passed in the system. He said, "SOA provides a more engineering, preset, and formal perspective that may meet a large number of important technical standards but is often considered to have ignored the most important issues: people are the center of software, and our data is irreplaceable and has great market advantages. Our software or service is like the power and network bandwidth in IT systems. It is very basic, but it does not have the most important value ." Many industry leaders say that enterprises also need the structure of SOA methods and the entrepreneurial capability of Web 2.0 methods. I helped prepare the analysis report of the recently held SOA execution conference and discussed the interactions between SOA and Web 2.0, especially mashup (a combination of multiple services ). I interviewed Miko Matsumura, vice president of SOA product marketing at webmethods, and he was very careful against the uncontrolled use of mashup because "This kind of infinitus is too authoritarian," he said: "This model is inherently less flexible and agile than a model with reasonable limits and is more expensive." Miko added that limited SOA management "should be considered as a pivot, rather than a 'body'. If you impose restrictions on one aspect, it does not mean that you cannot freely move in other directions. This is the balance presented by SOA, that is, the alliance between it and business. On the one hand, the other side wants to tighten the reins ." Dion points out some elements common to SOA and Web 2.0, and lists some common points: software restructuring management software is a service application. The platform unconsciously uses open Ajax for interoperability. monetization, security, network-oriented architecture. The last network-oriented architecture or woa is the key content, in the end, SOA and Web 2.0 may be integrated. Dion said: "In the largest discussion about traditional SOA, there are thousands of software platforms and environments on the surface. If they cannot talk to you in your SOA (soap and WS-*) mode, it is impossible to implement interoperability ." However, Dion also adds: "by using Woa, anyone can say http-the most basic network protocol-Anyone can process XML, that is to say, any existing tool and platform can achieve interoperability and simple, secure and easy to work together, and build applications on other services. Importantly, mashup is the key result towards Woa, and most mashups are based on rest or services similar to rest ." Mashups may occupy a more important position in SOA than we think. As part of the InfoWorld project, I interviewed the Software AG technology taidou mighael Botha, who thought: "I think mashup is the value of SOA. I can demonstrate mashup to users and say, "This is a technology that allows users within an organization to use software from the same perspective. Users may not understand what mashup is, but when they see that they can get all the data about customers or products from six or seven different systems in the background, they will understand ." Will Web 2.0 ultimately benefit SOA? Ashish mohindaroo, senior director of Oracle fusion middleware, believes: "Web 2.0 focuses on improving user productivity, while SOA focuses on Reusing existing assets. It would be good if I could break up the content of different websites and combine them into new pages or provide new services to end users ." He explained: "In the past, it may take longer for me to launch a new service, because all work should start from scratch ." View International Source SOA and Web 2.0: center of gravity transfer between edge and center http://dev2dev.bea.com.cn/blog/tigersoa/200708/20_421.htmlhttp://dev2dev.bea.com.cn/blog/tigersoa/200708/20_422.htmlhttp://dev2dev.bea.com.cn/blog/tigersoa/200708/22_431.html Web 2.0 and SOA: Web 2.0 introduction http://www.ibm.com/developerworks/cn/web/wa-web20soa1/
