Untitled

ARCHITECTURAL STYLE SOA

Service-oriented architecture (SOA) is a type of software design that allows its elements to be reused thanks to the service interfaces that communicate through a network with a common language.

How does service-oriented architecture work?

Before SOA came into use in the late 1990s, it was very difficult to connect an application with services hosted on another system, and deep end-to-end integration was required.

The developers then had to repeat the process for each new project. This model was known as "monolithic", since the code for the entire application was part of a single implementation.

Advantages over the monolithic approach

Faster time to market and greater flexibility

Using Legacy Infrastructure in New Markets

Cost reduction through greater agility and more efficient development

Easy maintenance

Scalability

Higher reliability

SOA Features

Proveedor de servicios

It is responsible for creating web services, offering them to a registry of available services and managing their conditions of use.

Agente o registro de servicios

It is responsible for providing information about the service to whoever requests it, and it can be public or private.

Usuario del servicio o persona que lo solicita

The user can search for a service in the registry or the agent, and will connect with the provider to receive it.

What are the fundamental design principles of a service-oriented architecture?

The components are coupled openly. A component that accesses another does not need to know data structures, calls to other components, transaction management, etc.

Components are configurable. Looking at a service-oriented architecture application like the one in the preceding diagram is similar to looking at a configuration diagram.

The components can work together. Any component can work with another, including components created by different vendor development environments.

Components are independent of location.