Marinade For Deer Sirloin Roast

Let's talk a little bit of SOA (Service Oriented Architecture)

After watching an introduction to EAI , we come to the next step which took place in view of the integration of information systems: solutions SOA (Service Oriented Architecture ). The popularity of the Web has led architectures tied to it through a big transformation from building simple web sites, corporate portals to solutions that integrate IT infrastructures.

the beginning of the study of problems of integration of applications we had the so-called distributed applications ( Object Oriented Architecture, OOA) components delivered with differences could cooperate with each other giving rise to a unique application according to standard protocols (eg CORBA, DCOM ). At this level the EAI acted: to interact with their applications / components completely heterogeneous.

There was, however, realized the benefits of a different approach to distributed services (web services) you could access these services by taking advantage of the interface that the web services provided under a contract (WSDL) and a protocol ( SOAP) standard. If these services could be searched for and discovered ( Discovered ) in a list of available services (UDDI). The advantage of this approach (SOA) than before (OOA) was that the focus was placed on functionality and not technology.

In other words, the SOA approach highlights an entity known mainly to corporate management than they were the technology implementations, which put the focus of the business process .

SOA is more complex architecture in WAS, although we can say that it can be also found on the technological concepts of WS. In reality, SOA is an abstraction layer top of a structure in WAS: we can say that SOA is

" A paradigm for the organization and utilization of distributed resources which may be under the control of different ownership domains. Provide a uniform to offer, discover, interact and use the ability to consistently produce the desired results with measurable preconditions and expectations "- Reference Model for Serviced Oriented Architecture 1.0." OASIS, 12 October 2006 ( Oasis is a global consortium founded in 1993 regulating the development and adoption of convergence of standard e-business).

SOA is thus a paradigm that translates into a dynamic architecture in which the design and development solutions are brought to higher levels of reasoning. These arguments make it possible to assess more fully the business processes, taken as a whole and not just individually, and, therefore, to seek the development of the best possible solution to deliver on business operations requirements.

So SOA is not a technology, but an architectural approach built around the existing technologies. It promotes a set of practices, disciplines, drawing mode and guidelines that can be applied using one or more technologies. SOA aims to develop new services based on features already offered by an application. Other applications that wish to communicate with this application will use one or more services to accomplish the task desired.

The SOA paradigm is based on three basic concepts:

• Visibility: ability to find the service best suited to your needs
• Interaction: ability to request a service and consequently esaudizione the request by the exchange of messages.
• Real effects: the ability to give results of the interaction.

Note how these concepts are not simply define the properties of a service: a service is delivered when carrying out activities on behalf of an applicant ( service consumer). The server ( service provider) provides its service offering, its ability to perform and the specifications with which you can successfully invoke the service. The description of the servant is made public through a discovery agency ( service broker), a repository or directory.

SOA is one of the latest paradigms of Web Engineering : generation of services and creation of conditions for the mechanization of the processes within the asset company information through the composite applications. Choosing a SOA solution than a means to take for architecture OOA these properties:

• Effective reuse and better "granularity" of services
• Interoperability of services and their services in componentization simpler (composite application)
• Taking generic standards and / or specific to certain domains
• Identification and accessibility of services standardized
• Monitoring Solution (IT governance )
• encapsulation services
• weak coupling between services ( loose coupling) using standard XML messages
• rules of interaction between the services under contracts established
• Increased abstraction from the logical implementation
• Possibility of subdivision services for macro-features of each service
• autonomy in determining its own implemented logic
• Traceability of services through constructs known and standard

Simplistically we can say that re-contextualizes the SOA paradigm OOA born with the network and the Internet. I introduced new levels of abstraction can greatly reduce the present gap between the logic of business processes and IT systems.

Scheme modular SOA