scholarly journals Best Practice Service-Oriented Architecture (SOA): Recommendation and Tips

2011 ◽  
Vol 2 (2) ◽  
pp. 783
Author(s):  
Maria Seraphina Astriani
Keyword(s):  
Best Practices ◽  
Best Practice ◽  
Service Oriented Architecture ◽  
Application Integration ◽  
Business Goals ◽  
Service Oriented ◽  
Business Functions ◽  
Integration Problems

Companies that have many applications always deal with application integration problems. For the of company necessity, they often yearn for information that an application can be used by other applications. Often a small portion of data from another application is needed in order to complete and support other business functions. They require an architectural approach that can bridge the information between applications. SOA (Service-Oriented Architecture) offers manufacturing services around existing business functions. Applications that wish to communicate with other applications can use the services to achieve business goals. This article will discuss recommendations and tips for implementing SOA best practices in banking. 

Beyond SOA and REST for Distributed Application Integration

2018 ◽  
pp. 228-257
Author(s):  
José Carlos Martins Delgado
Keyword(s):  
Service Oriented Architecture ◽  
Fundamental Problem ◽  
Application Integration ◽  
Distributed Application ◽  
Representational State Transfer ◽  
Architectural Styles ◽  
State Transfer ◽  
Service Oriented ◽  
Structural Compliance ◽  
Application Specific

The fundamental problem of distributed application integration is reducing application coupling as much as possible while still meeting the minimum interoperability requirements. Service-oriented architecture (SOA) and representational state transfer (REST) are the most used architectural styles to deal with this problem. This chapter performs a comparative study of these styles and shows that, while both solve basic interoperability, neither of them minimizes coupling, since data description schemas are shared by the interacting applications (symmetric interoperability). SOA is oriented towards behavior (services) and REST towards state (structured resources). Services have no structure and resources have a fixed service. This chapter proposes a new architectural style, structured services, that combines the best characteristics of SOA and REST (services can have structure and resources can implement application-specific services), while using asymmetric interoperability (schema compatibility is based on structural compliance and conformance) to minimize application coupling.

Improving Application Integration by Combining Services and Resources

2019 ◽  
pp. 197-226 ◽  
Author(s):  
José Carlos Martins Delgado
Keyword(s):  
Service Oriented Architecture ◽  
Application Integration ◽  
Architectural Style ◽  
Representational State Transfer ◽  
Architectural Styles ◽  
State Transfer ◽  
Fixed Set ◽  
Service Oriented ◽  
Application Developers ◽  
Bare Minimum

The main application integration approaches, the service-oriented architecture (SOA) and representational state transfer (REST) architectural styles, are rather different in their modeling paradigm, forcing application developers to choose between one and the other. In addition, both introduce more application coupling than required, since data schemas need to be common, even if not all instantiations of those schemas are used. This chapter contends that it is possible to improve this scenario by conceiving a new architectural style, structural services, which combines services and resources to reduce the semantic gap with the applications, allowing to tune the application integration between pure service-based and pure resource-based, or an intermediate mix. Unlike REST, resources are not constrained to offer a fixed set of operations, and unlike SOA, services are allowed to have structure. In addition, compliance is used to reduce coupling to the bare minimum required by the actually used application features.

Service-Oriented Computing

2013 ◽  
pp. 1-20 ◽  
Author(s):  
Stéphanie Chollet ◽  
Philippe Lalanda ◽  
Jonathan Bardin
Keyword(s):  
Web Services ◽  
Service Oriented Architecture ◽  
Application Integration ◽  
New Paradigm ◽  
Loosely Coupled ◽  
Service Oriented Computing ◽  
Service Oriented ◽  
Scale Network ◽  
Computing Platforms ◽  
Multiple Domains

The visionary promise of Service-Oriented Computing (SOC) is a world-scale network of loosely coupled services that can be assembled with little effort in agile applications that may span organizations and computing platforms. In practice, services are assembled in a Service-Oriented Architecture (SOA) that provides mechanisms and rules to specify, publish, discover and compose available services. The aim of this chapter is to present the different technologies implementing the new paradigm of SOA: Web Services, UPnP, DPWS, and service-oriented component OSGi and iPOJO. These technologies have been developed and adapted to multiple domains: application integration, pervasive computing and dynamic application integration.

Towards Automated SLA Management for Service Delivery in SOA-based Environments

2016 ◽  
Vol 7 (1) ◽  
pp. 26-40
Author(s):  
Elarbi Badidi ◽  
Mohamed El Koutbi
Keyword(s):  
Service Oriented Architecture ◽  
Service Providers ◽  
Service Level ◽  
Third Party ◽  
Handheld Devices ◽  
Service Provisioning ◽  
Functional Requirements ◽  
Business Goals ◽  
Sla Negotiation ◽  
Service Oriented

The services landscape is changing with the growing adoption by businesses of the Service Oriented Architecture (SOA), the migration of business solutions to the cloud, and the proliferation of smartphones and Internet-enabled handheld devices to consume services. To meet their business goals, organizations increasingly demand services, which can satisfy their functional and non-functional requirements. Service Level Agreements (SLAs) are seen as the means to guarantee the continuity in service provisioning and required levels of service. In this paper, we propose a framework for service provisioning, which aims at providing support for automated SLA negotiation and management. The Service Broker component carries out SLA negotiation with selected service-providers on behalf of service-consumers. Multi-rounds of negotiations are very often required to reach an agreement. In each round, the negotiating parties bargain on multiple SLA parameters by trying to maximize their global utility functions. The monitoring infrastructure is in charge of observing SLA compliance monitoring using measurements obtained from independent third party monitoring services.

Integration Platform for De-Centralized Investment Projects Appraisal

2007 ◽  
pp. 329-349
Author(s):  
M. Stanojevic
Keyword(s):  
Service Oriented Architecture ◽  
Investment Decision ◽  
Integration Platform ◽  
Investment Projects ◽  
Geographically Dispersed ◽  
Investment Decision Making ◽  
Service Oriented ◽  
Concise Information ◽  
Integration Problems ◽  
Insight Into

In this chapter, a few software architectures and platforms are discussed in relation with their ability to cope with business integration problems in large, geographically dispersed companies. Of these architectures, the three-tier architecture has reached maturity and proved its usefulness in solving these problems. As an illustration of its usefulness, two successful applications of the three-tier architecture, based on Java 2 Platform Enterprise Edition (J2EE), solving business integration problems inherent to investment decision-making in large companies, Framework for Investment Decision Support (FIDES) and ProjectsAnywhere, are described in detail. For solving more complex business integration problems, Service Oriented Architecture (SOA), based on agent or Web services approach, is recommended. Hopefully, this chapter will provide concise information about architectures and platforms, and an insight into two complex applications based on them, that will be useful in developing other complex applications that face similar business integration problems.

Service-Oriented Architecture

2009 ◽  
pp. 130-150
Author(s):  
Matthew Guah
Keyword(s):  
Web Services ◽  
Service Oriented Architecture ◽  
Software Components ◽  
Application Integration ◽  
Separation Of Concerns ◽  
Enterprise Service Bus ◽  
Exchange Information ◽  
Integration Techniques ◽  
Service Oriented ◽  
Host Organization

For centuries, organizations have been trying to exchange information between their applications by linking them together. However, such application integration has not been as successful as organizations have hoped. With the introduction of SOA, application integration is more successful than the previous integration techniques. SOA is a design philosophy in which resources are cleanly partitioned into remotely accessible software components performing self-contained functionalities, called services. The reinvention of SOA in recent times is attributed to the rise of Web Services, which has become commonly used in VLITP to expose services within the host organization. However SOA can also be implemented with other service exposing techniques. SOA is based on the concept of separation of concerns, realizing that no single entity can be best at everything. SOA is usually implemented using an Enterprise Service Bus (ESB). The ESB is responsible for routing, prioritizing, scheduling, monitoring, and controlling the flow of traffic between services and therefore forms the middleware for Service Orientation.

SOA Governance Considerations for Successful Project Management

2015 ◽  
pp. 245-264
Author(s):  
Konstantinos Koumaditis ◽  
Marinos Themistocleous
Keyword(s):  
Success Factors ◽  
Service Oriented Architecture ◽  
It Projects ◽  
Critical Success ◽  
It Flexibility ◽  
Business Goals ◽  
Service Oriented ◽  
Research Findings ◽  
Research Gap ◽  
Systematic Synthesis

Information Technology (IT) projects are more and more aligned with business goals. Service Oriented Architecture (SOA) was introduced to achieve this, align business with IT, and increase IT flexibility, reuse of services in more manageable way. Unfortunately, healthcare organisations that have adopted SOA have yet to benefit from their investment. Industry analysts and academics agree that SOA Governance is a critical success factors for SOA projects. Addressing the substantial research gap, this chapter investigates longstanding challenges and proposes a SOA Governance framework as a way to improve IT/SOA success and guide the alignment of IT and business. The authors present a systematic synthesis of the latest research findings and professional experience on SOA Governance considerations for successful IT projects.

Business Process Modeling with Services

2013 ◽  
pp. 177-200
Author(s):  
Youcef Baghdadi ◽  
Naoufel Kraiem
Keyword(s):  
Reverse Engineering ◽  
Business Process ◽  
Process Modeling ◽  
Business Processes ◽  
Service Oriented Architecture ◽  
Source Code ◽  
Legacy Systems ◽  
Service Oriented ◽  
Business Functions ◽  
Maintenance Process

Reverse engineering techniques have become very important within the maintenance process providing several benefits. They retrieve abstract representations that not only facilitate the comprehension of legacy systems but also refactor these representations. Business process archaeology has emerged as a set of techniques and tools to recover business processes from source code and to preserve the existing business functions and rules buried in legacy source code. This chapter presents a reverse engineering process and a tool to retrieve services from running databases. These services are further reused in composing business processes with respect to Service-Oriented Architecture, a new architectural style that promotes agility.

Sign in / Sign up

Export Citation Format

Share Document