Service-Oriented Architecture (SOA)

SOA Architecture Basics Concepts

Service-Oriented Architecture (SOA)

Before delving into what a service-oriented architecture (SOA) is, create some basic concepts and terms that are not strictly defined, so perhaps some definitions remain controversial in the industry and are ignored for the moment.

Architecture Basics

Technical Architecture (technology Architecture)--Basic physical design of something (the fundamental of physical design of something)

Technical infrastructure (technology Infrastructure) – a basic and supportive technology environment, including software and hardware (the underlying, supporting technology environment, including software and hardware)

software programs (software program)-a standalone system that can be a custom-developed application, or a purchased product application (a standalone system, may custom-developed Application or a purchased product)

Classic analogy of the relationship between architecture and infrastructure

The term "architecture" in the IT domain stems from the design and construction of buildings and structures. This origin also provides a good analogy for us to differentiate between the technical architecture (technology Architecture) and the technical infrastructure (technology Infrastructure). The physical design of a building is documented in its architectural blueprint and specification. But the building is in the environment around it, and the surrounding environment may provide a lot of support for the building to meet the purpose of its construction, or it may just be the opposite. For example, in the city of office buildings or residential buildings around the streets, power stations, cables, drainage systems and other related resources can be provided. These can be thought of as the technology infrastructure in the IT area (technology Infrastructure).

In order to make use of these infrastructures, the physical design of the building will be part of the formal architecture design. As a result, the design code for a building will include the infrastructure associated with it. To sum up, there is no clear boundary between the architecture of the building and the environmental infrastructure, and this overlapping phenomenon also exists in the IT field.

Technical Architecture (Technology Architecture)

The scope of the technical architecture varies from one design object to another, and some of the more common types are:

Component Architecture (Component Architecture)-In a distributed computing environment, the component architecture is primarily the physical architecture of a single software program.

Application Architecture (Application Architecture)--an application or system in which a deployment environment has a physical boundary limit. In a distributed computing environment, the application architecture includes multiple component architectures.

Integrated architecture (Integration Architecture)--Two and more associated applications or system technical architectures, including technology, resources, and extensions that integrate them. Many integration architectures include the middleware platform and the extension of the associated adapter bridging.

Enterprise Technology Architecture-unlike components, applications, and integration architectures, it is in the design documentation that is recorded before the program is created. It usually exists in the form of a document in an enterprise environment. An enterprise Technical architecture specification includes all the forms of architecture described earlier, as well as official documentation of the enterprise infrastructure.

Technical infrastructure

In a typical it enterprise, the technical infrastructure represents the target environment for software program deployment. So the term "architecture", infrastructure can be classified as "software" or "hardware"

Hardware infrastructure typically includes:

Servers and workstations (servers and workstations)

Routing, firewalls, and network devices (Routers,firewalls,and networking equipment)

Backup power supply facilities, cables and other computer equipment (back-up power Supplies,cables,and other computer equipment)

Software infrastructure typically includes:

Operating system and System application excuses (operating systems and systems APIs)

Runtime environment and system-level service proxies (runtime environments and System-level service agents)

Databases and file directories (database and directories)

Middleware and adapters (middleware and adapters)

User account management and security technology (management and technologies)

software programs (software program)

A software program is simply a system, an application, or a solution that exists. It can be either a purchased product or a customized program. Its relationship to the technical architecture is that the software program can be seen as an implementation of the architecture specification design document and also in the support environment that exists in the technical architecture description.

Part of the software program design is recorded in the application architecture specification, it is mainly to emphasize the overall structure of the program (including the component information it contains), technology and resource requirements. Therefore, a typical application architecture typically complements the design documentation, such as the functional specification of the interpretation process, the user interface style, and the detailed program execution path algorithm.

Reference: The SOA design model was co-authored by Thomas Erl and other contributors as part of Thomas Erl's service-oriented Computing series, published by Prentice Hall in January 2009, ISBN 0136135161, all rights reserved SOA System INC.

Service-Oriented Architecture (SOA)