 |
For more information on Pallas Consulting LLC and the services offered, please feel free to contact us directly. We look forward to hearing from you. |
|
|
|
Service Oriented
Architecture |
In computing, the term Service Oriented Architecture (SOA) expresses a software architectural
concept that defines the use of services to support the requirements of software users. Based
on a SOA environment, computers on a network make resources available to other participants in
the network as independent services that the participants access in a standardized way. Most
definitions of SOA identify the use of Web services (i.e. using SOAP) in its implementation.
However, one can implement SOA using any service-based technology.
Unlike traditional point-to-point architectures, SOAs comprise of loosely coupled, highly
interoperable application services. These services interoperate based on a formal definition
independent of the underlying platform and programming language (e.g., - WSDL). The interface
definition encapsulates (hides) the vendor and language-specific implementation. A SOA is
independent of development technology (such as Java and .NET). The software components
become very reusable because the interface is defined in a standards-compliant manner. So, for
example, a C# service can be used by a Java application.
|
|
|
|
|
Why SOA? |
Enterprise architects believe that SOAs help businesses respond more quickly and cost-
effectively to the changing market conditions they may face by promoting reuse of existing IT
assets rather than more time consuming and costly reinvention.
|
|
|
|
Enterprise
Service Bus |
An enterprise service bus refers to a software architecture construct, implemented by
technologies found in a category of middleware infrastructure products usually incorporating Web
services standards, that provides foundational services for more complex Service Oriented
Architectures (SOA) via an event-driven and XML-based messaging infrastructure (the bus). An
Enterprise Service Bus provides an abstraction layer on top of an Enterprise Messaging System
(JMS) which allows integration architects to exploit the value of messaging without writing code.
|
|
|
|
Enterprise Application
Integration |
Enterprise Application Integration has increased in importance because, traditionally, enterprise
computing often takes the form of islands of automation. This occurs when the value of individual
systems are not maximized due to partial or full isolation. If integration is applied without following
a structured EAI approach, many point-to-point connections grow up across an organization.
Dependencies are added on an impromptu basis, resulting in a tangled, difficult to maintain, mess.
This is commonly referred to as spaghetti integration, which is a comparison to spaghetti code, the
programming equivalent.
|
|
|
|
| |
|
