slow and unstable;
(C) the version of the service cannot be upgraded, or even the machines on the Internet cannot directly or indirectly use a service.
The SOA architecture has some typical features, including loose coupling, location transparency, and Protocol independence. Loose coupling requires that different services in the
Document directory
New SOA business language new system architecture-SOA and BPM
SOA new business language New System Architecture -- in the wave of joint development of SOA and BPM, we must first clarify that the nature of BP
Document directory
New SOA business language New System Architecture -- building SOA
IBM
Microsoft
SOA concept, technology and design
SOA new business language new system architecture-building
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
Document directory
New SOA business language new system architecture-SOA and SaaS
New business language and new system architecture of SOA-SOA and SaaS begin to introduce some new obfuscation with the increasing popularity of
This article will continue the first part and introduce the impact of SOA on enterprise-level architecture design, and how to ensure that the system architecture can meet different service level requirements in the system when building an enterprise system based on SOA.
1. The impact of
Document directory
General Service-oriented principle --- from Chapter 8 of SOA concepts, technologies and Design
WCF programming-service-oriented overview
Architecture Principles
Practical principles
SOA new business language new system architecture-SOA principles
Document directory
Service-oriented value (from the book of WCF programming)
For the purpose of SOA, IBM says:The fundamental purpose of SOA is business agility. How to understand agility is understood from two aspects: first, it responds to this change in an appropriate period of time after the business changes are proposed; second, changes made by it can properly reflect business needs.
Microsoft sai
Introduction to Event-driven architecture (Event-driven Architecture,eda)There are two ways to understand EDA:
EDA is an architectural pattern that focuses on generation/consumption-based asynchronous communication. This is mainly compared to traditional thread-based synchronization systems.
EDA is a kind of architecture mode which takes event as the
have different requirements for analysis and design execution.There is a saying that I think is very enlightening to architects: analysis is to do the right thing, design is right to do things. Architecture is not the language with the platform, after all, architecture is a sub-process in the design process, I think if your design is unreasonable, you can use any language platform can not solve the problem
different contexts have different requirements for analysis and design execution.There is a saying that I think is very enlightening to architects: analysis is to do the right thing, design is right to do things. Architecture is not the language with the platform, after all, architecture is a sub-process in the design process, I think if your design is unreasonable, you can use any language platform can no
in different ways, operating systems and programming languages;
B) massive and frequent data transmission is still slow and unstable;
C) The version upgrade cannot be completed, and we cannot know which machines on the Internet directly or indirectly use a service.
Based on the above premise, let's take a look at the basic features of SOA.
Three basic features of SOA
http://www.ibm.com/developerworks/cn/webservices/ws-arcsoa1/
SOA (service-oriented Architecture), a service-oriented architecture, is the most common word in a variety of technical journals in the last year or two. There are now many architects and design developers who simply equate SOA and Web services technology wi
Service-Oriented Architecture) is a service-oriented architecture. This is the most frequently used word in a variety of technical journals in the past one or two years. Currently, many architecture designers and design developers simply equate SOA with Web Services, and think SOA
and CORBA. The difference between the service-oriented architecture of web services today and the past is that they are standards-based and loosely coupled. Widely accepted standards (such as XML and SOAP) provide interoperability between solutions of different vendors. Loose coupling isolates participants in distributed computing, and changes made by one party on both sides of the interaction will not affect the other. The combination of the two mea
Introduction
More and more customers are often asked to complete projects that do not use SOA at all, but to implement the Enterprise Service Bus (BUS,ESB) architecture only. This type of ESB-oriented architecture is not difficult, but its success is hard to conclude. Customers who require such projects are not aware of this: an ESB-oriented
and CORBA. The difference between the service-oriented architecture of web services today and the past is that they are standards-based and loosely coupled. Widely accepted standards (such as XML and SOAP) provide interoperability between solutions of different vendors. Loose coupling isolates participants in distributed computing, and changes made by one party on both sides of the interaction will not affect the other. The combination of the two mea
A Reference Architecture (SOA) is a framework that enables each project to have a compliance basis to promote consistency, best practices, and standardization. The reference architecture is not limited by the current IT status, but should be targeted at a well-thought-out vision. IT can be said that IT guides all future development work and serves as a reference
From: http://newhappy2008.blog.sohu.com/117231212.html
A Reference Architecture (SOA) is a framework that enables each project to have a compliance basis to promote consistency, best practices, and standardization. The reference architecture is not limited by the current IT status, but should be targeted at a well-thought-out vision. It can be said that it guides
accepted standards, such as XML and SOAP, provide interactivity between different vendor solutions. Loose coupling separates the participants in the distribution calculation, and the changes on either side of the interaction do not affect the other. The combination of the two means that companies can implement certain Web services without having any knowledge of the clients that use those Web services. We call this standards-based, loosely coupled, service-oriented
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.