(Next: Architecture Design: Inter-system Communication (34)-The deified ESB (UP))2-4. ESB and version controlThe process of system integration in enterprises, there are many non-technical factors caused by the change. It is possible that a call function A, which has been able to function normally, is suddenly not available on one day. The technical team and the b
Application Server 6 to build an enterprise's ESB to support the SOA system architecture. The underlying framework to be selected to implement the SOA system architecture depends on the characteristics of each system. However, these underlying frameworks have provided high
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
Part-1 "Brief Introduction" 1. through the introduction of Service Oriented Architecture (SOA), Enterprise Service Bus (ESB), adapter (Adapter) and component-oriented technology, try to build a unified business process Service platform to realize process-oriented service integration. 2. The focus of traditional banking informatization is basically the constructio
, in the technology of microcomputer, there are three kinds of bus, address bus Address bus, data bus of the bus, control buses. In the communication architecture, the switch is also a kind of bus, in the SOA, the bus generally refers to enterprise service Bus (ERP), Enterprise service Bus can connect the various interfaces of all protocols, but the most ideal is XML-based WEB service standards (BUS,
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
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
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
policy
Specifications for service and data model adoption
Service lifecycle Definition
Specifications related to service infrastructure, such as Enterprise Service Bus (ESB), business process management (BPM), Registry, and Repository, including:
What deployment configurations must be supported?
What capabilities are required?
Responsibilities of various components
The coupling relationship and principles between components s
PolicyService version control policySpecifications for service and data model adoptionService lifecycle Definition
2. specifications related to service infrastructure, such as Enterprise Service Bus (ESB), business process management (BPM), registry, and repository, including:What deployment configurations must be supported?What capabilities are required?Responsibilities of various componentsThe coupling relationship and principles between components
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
ESB Architecture Model
ESB is the intermediary between the client that calls the service and the provider of the service. It is responsible for handling the connection tasks between them, thus simplifying the client and the provider. IBM standards and opennessSource codeVice President Robert Sutor described in his blog eight defining principles that must be embo
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
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
. To ensure that servicea can run normally, serviceb must be available at the same time before servicea can run properly. This is a highly space-time coupling. On the contrary, if servicea does not have serviceb and can still run normally, this is a low space-time coupling.An asynchronous web-service call is an example of high space-time coupling.
Now you may have doubts: In a use case, servicea and serviceb services are required. So, how do they do it separately?The answer is: Use a queue for
[It168 technical analysis comment]Recently, itpubCommunityIn the ERP section, a user who has been using ERP for many years, Li Xin (not his real name), complained that U9 was using a large number of stored procedures, I also question the world's first SOA-Based ERP system U9. What is the concept of its SOA design architecture reflected in?
The information-relat
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
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
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.