Comparing Architectural Styles for Service-Oriented Architectures – a REST vs. SOAP Case Study

2009 ◽  
pp. 207-215 ◽  
Author(s):  
Jörg Becker ◽  
Martin Matzner ◽  
Oliver Müller
Keyword(s):  
Service Oriented Architectures ◽  
Architectural Styles ◽  
Service Oriented

Design of Quality Aspects in Service Oriented Architecture through Service Level Agreements

2011 ◽  
pp. 1-21
Author(s):  
Marco Massarelli ◽  
Claudia Raibulet ◽  
Daniele Cammareri ◽  
Nicolò Perino
Keyword(s):  
Service Oriented Architecture ◽  
Service Level ◽  
Application Domain ◽  
Service Level Agreements ◽  
Actual Case ◽  
Service Oriented Architectures ◽  
Quality Aspects ◽  
Service Oriented

This chapter gives a solution to design Service Oriented Architectures which defines and manages Service Level Agreements to enforce Quality of Services and achieves adaptivity at runtime. The validation of this proposed approach is performed through an actual case study in the context of the multimedia application domain.

An Evolutive Component-Based Method for Agile Development of Service Oriented Architectures

2017 ◽  
Vol 9 (3) ◽  
pp. 37-57 ◽  
Author(s):  
Hamza Chehili ◽  
Lionel Seinturier ◽  
Mahmoud Boufaida
Keyword(s):  
Development Process ◽  
Business Processes ◽  
Agile Development ◽  
Service Oriented Architectures ◽  
Development Method ◽  
Service Oriented ◽  
Agile Software Engineering ◽  
Agile Software ◽  
Incremental Process

The adoption of the agile methods' principles has emerged as an effective way to develop service oriented architectures as it paves the way for a better reply to the changing needs of the environment and even the customer. However, these changes may also require the evolution of the development process itself. This paper presents an agile and service-oriented software development method that combines concepts from the Service-Oriented Computing (SOC) domain and the agile software engineering one. This method provides an iterative and incremental process to deliverer business processes, implemented as an assembly of components. This leads to a faster response to the change of needs by reconfiguring the assembly of components. The method is based on a framework that implements its phases as an assembly of components to allow a dynamic reconfiguration of it in case of a development process evolution. Finally, a case study is presented to illustrate the use of the presented method.

scholarly journals Resource and service discovery in SOAs: A P2P oriented semantic approach

2011 ◽  
Vol 21 (2) ◽  
pp. 285-294 ◽  
Author(s):  
Giuseppe Di Modica ◽  
Orazio Tomarchio ◽  
Lorenzo Vita
Keyword(s):  
Service Discovery ◽  
Semantic Approach ◽  
Service Oriented Architectures ◽  
Technological Convergence ◽  
Service Oriented ◽  
Standardization Process ◽  
System Prototype ◽  
Grid Resources ◽  
Administrative Domains

Resource and service discovery in SOAs: A P2P oriented semantic approachAn intense standardization process is favouring the convergence of grids and Service Oriented Architectures (SOAs). One of the benefits of such technological convergence is that grid resources and applications can be virtualized by services and offered through the SOA paradigm. In the broad and interoperable scenarios enabled by the SOA, involving the participation of several grid infrastructures across many administrative domains, service discovery can be a serious issue. In this paper we present a P2P-based infrastructure that leverages semantic technologies to support a scalable and accurate service discovery process. The key concept of the presented idea is the creation of an overlay network organized in several semantic groups of peers, each specialized in answering queries pertaining to specific applicative domains. Groups are formed by clustering together peers offering services that are semantically related. The architecture details of the proposed solution are presented. A system prototype has also been implemented and validated through a case study deployed on the PlanetLab testbed.

A MODEL-DRIVEN APPROACH TO WEAVE ARCHITECTURAL STYLES INTO SERVICE-ORIENTED ARCHITECTURES

2011 ◽  
Vol 20 (02) ◽  
pp. 201-220 ◽  
Author(s):  
MARCOS LÓPEZ-SANZ ◽  
JUAN MANUEL VARA ◽  
ESPERANZA MARCOS ◽  
CARLOS E. CUESTA
Keyword(s):  
Software Engineering ◽  
Architectural Style ◽  
Service Oriented Architectures ◽  
Model Driven Development ◽  
Model Driven ◽  
Architectural Styles ◽  
Architectural Model ◽  
Service Oriented ◽  
Architectural Models ◽  
Model Driven Approach

Model-driven development is recognized as one of the most promising approaches in software engineering. Recent research in the area highlights the importance of using an explicit architectural model in this context. Since service-oriented architectures have also demonstrated to be adequate to overcome current software needs, the idea of using the model-driven approach to generate service-oriented architectural models has successfully flourished in the last years. However, the emphasis on the Service-Oriented Computing (SOC) paradigm has led to the design of architectures lacking some desirable features. Knowing the benefits provided by architectural styles, we have found that their use can help us to overcome those needs. Our goal is to obtain a service-oriented model which satisfies the requirements of the concrete architecture and complies with the constraints and vocabulary defined for a specific architectural style. To achieve this, here, we propose to use a weaving model which merges the concrete architectural model with a model of the architectural style of choice.

The SOA Frontier

2012 ◽  
pp. 126-152 ◽  
Author(s):  
Juan M. Rodriguez ◽  
Marco Crasso ◽  
Cristian Mateos ◽  
Alejandro Zunino ◽  
Marcelo Campo ◽  
...  
Keyword(s):  
Web Services ◽  
Service Oriented Architecture ◽  
Current Trend ◽  
Service Oriented Architectures ◽  
Trade Off ◽  
Advantages And Disadvantages ◽  
Service Oriented ◽  
Migration Costs ◽  
Common Situation

Service Oriented Architecture (SOA) and Web Services are the current trend to integrate large and distributed systems, which is a common situation in both the business and government worlds. However, within these worlds, systems are commonly written in COBOL because they were developed several decades ago. Therefore, migration of COBOL systems into service-oriented architectures becomes a necessity. Two main approaches are used to migrate COBOL systems to SOA systems: direct and indirect migration. Direct migration implies wrapping the current COBOL routines of a system with a software layer developed under a newer platform that can be used to offer Web Services. In contrast, indirect migration requires re-designing and re-implementing the COBOL routines’ functionality using a newer platform as well. In this chapter, the authors propose a novel migration approach, which takes the best of the two previous approaches. To assess the advantages and disadvantages of these approaches, this chapter presents a case study from a government agency COBOL system that has been migrated to a Web services-based system using the three approaches. As a result of having these migration attempts, the authors present the trade-off between direct and indirect migration, the resulting service interfaces quality, and the migration costs. These results also show that this new migration approach offers a good balance to the above trade-off, which makes the approach applicable to similar COBOL migration scenarios.

Automatic Determination of Compatibility in Evolving Services

2011 ◽  
Vol 8 (1) ◽  
pp. 21-40 ◽  
Author(s):  
Karin Becker ◽  
Jim Pruyne ◽  
Sharad Singhal ◽  
Andre Lopes ◽  
Dejan Milojicic
Keyword(s):  
Automatic Determination ◽  
Service Oriented Architectures ◽  
Loosely Coupled ◽  
Service Oriented ◽  
Run Time ◽  
The Impact

A major advantage of Service-Oriented Architectures (SOA) is composition and coordination of loosely coupled services. Because the development lifecycles of services and clients are de-coupled, multiple service versions must be maintained to support older clients. Typically versions are managed within the SOA by updating service descriptions using conventions on version numbers and namespaces. In all cases, the compatibility among services descriptions must be evaluated, which can be hard, error-prone and costly if performed manually, particularly for complex descriptions. In this paper, the authors describe a method to automatically determine when two service descriptions are backward compatible. The authors describe a case study to illustrate version compatibility information in a SOA environment and present initial performance overheads. By automatically exploring compatibility information, a) service developers can assess the impact of proposed changes; b) proper versioning requirements can be put in client implementations guaranteeing that incompatibilities will not occur during run-time; and c) messages exchanged in the SOA can be validated to ensure that only expected messages or compatible ones are exchanged.

Engineering a Service-Oriented Architecture in E-Government

2005 ◽  
pp. 340-352
Author(s):  
Marijn Janssen
Keyword(s):  
Service Oriented Architecture ◽  
Legacy Systems ◽  
Public Servants ◽  
Service Oriented Architectures ◽  
Quality Requirements ◽  
Share Data ◽  
Service Oriented ◽  
New Applications ◽  
Further Development

Service-oriented enterprise architectures have gained considerable attention of politicians and public servants as a solution for designing new applications and leveraging investments in legacy systems. Service-oriented architectures can help to share data and functionality among information systems and provide the flexibility to include existing legacy systems, which cannot be replaced easily and otherwise restrict further development. In this chapter, the design of a service-oriented architecture in public administration is explored. A case study is conducted at the Ministry of Justice, and a service-oriented architecture is designed, implemented, and evaluated. The architecture is evaluated based on a number of quality requirements. This case study shows the feasibility to replace functionality formerly offered by legacy systems and shows limitations of current technology. This chapter should lead to a greater understanding of the concept of service-oriented architectures in e-government.

Sign in / Sign up

Export Citation Format

Share Document