Web 2.0

2010 ◽  
pp. 119-134
Author(s):  
Wail M. Omar
Keyword(s):  
Grid Computing ◽  
Web 2.0 ◽  
Health Information ◽  
Service Oriented Architecture ◽  
Bottom Layer ◽  
End Users ◽  
Web 2.0 Technology ◽  
Enterprise Applications ◽  
Service Oriented

Web 2.0 is expected to be the next technology in the interaction between the enterprise applications and end users. Such interaction will be utilized in producing self-governance applications that are able to readjacent and reconfigure the operation framework based on users’ feedback. To achieve this, huge numbers of underneath resources (infrastructures and services) are required. Therefore, this work proposes the merge of Web 2.0 technology and grid computing overlay to support Web 2.0 framework. Such merge between technologies is expected to offer mutual benefits for both communities. Through this work, a model for managing the interaction between the two technologies is developed based on the adapting of service oriented architecture (SOA) model, this model is known as SOAW2G. This model manages the interaction between the users at the top level and resources at the bottom layer. As a case study, managing health information based on users’ (doctors, medicine companies, and others) experiences is explored through this chapter.

Healthcare Collaborative Framework Based on Web 2.0, Grid Computing and SOA

2012 ◽  
pp. 429-452
Author(s):  
Wail M. Omar
Keyword(s):  
Grid Computing ◽  
Web 2.0 ◽  
Service Oriented Architecture ◽  
Data Availability ◽  
Healthcare Applications ◽  
Storage Devices ◽  
Robust Model ◽  
Enterprise Applications ◽  
Open Standard ◽  
Service Oriented

Web 2.0 has been adopted by many as the best way for forming a collaborative framework e.g., sharing resources, experiences, information, knowledge and feedback. A collaborative framework for application to e-health is necessary to provide patients with the awareness that assists in improving their health. Moreover, collaborative framework can be used by physician to exchange experiences and discuss challenge cases. However, the use of Web 2.0 with healthcare applications is not simple as the use of Web 20 with other enterprise applications according to the privacy of healthcare applications, which requires high quality and security of data, availability of resources, maintainability of services, system security, and Quality of Services (QoS). To offer the required requirements, grid computing is proposed here. Grid computing supporting enterprise applications through offering massive resources through resources collaborative framework that is offering power computing, storage devices, and services. The use of grid computing by Web 2.0 requires robust model that is able to deploy, discover, invoke, and integrate resources in open standard format. Therefore, Service Oriented Architecture (SOA) is adopted as a model for managing the mixing between Web 2.0 and grid computing technologies. SOA for Web 2.0 and Grid Computing (SOAW2G) are used throughout this work to offer a fabric for e-health applications.

Healthcare Collaborative Framework Based on Web 2.0, Grid Computing and SOA

2010 ◽  
pp. 190-212
Author(s):  
Wail M. Omar
Keyword(s):  
Grid Computing ◽  
Web 2.0 ◽  
Service Oriented Architecture ◽  
Data Availability ◽  
Healthcare Applications ◽  
Storage Devices ◽  
Robust Model ◽  
Enterprise Applications ◽  
Open Standard ◽  
Service Oriented

Web 2.0 has been adopted by many as the best way for forming a collaborative framework e.g., sharing resources, experiences, information, knowledge and feedback. A collaborative framework for application to e-health is necessary to provide patients with the awareness that assists in improving their health. Moreover, collaborative framework can be used by physician to exchange experiences and discuss challenge cases. However, the use of Web 2.0 with healthcare applications is not simple as the use of Web 20 with other enterprise applications according to the privacy of healthcare applications, which requires high quality and security of data, availability of resources, maintainability of services, system security, and Quality of Services (QoS). To offer the required requirements, grid computing is proposed here. Grid computing supporting enterprise applications through offering massive resources through resources collaborative framework that is offering power computing, storage devices, and services. The use of grid computing by Web 2.0 requires robust model that is able to deploy, discover, invoke, and integrate resources in open standard format. Therefore, Service Oriented Architecture (SOA) is adopted as a model for managing the mixing between Web 2.0 and grid computing technologies. SOA for Web 2.0 and Grid Computing (SOAW2G) are used throughout this work to offer a fabric for e-health applications.

Integrating Web 2.0 and RESTful Web Services in Enterprise Grids

2015 ◽  
pp. 167-190
Author(s):  
Qusay F. Hassan
Keyword(s):  
Web Services ◽  
Grid Computing ◽  
Web 2.0 ◽  
Paradigm Shift ◽  
Service Oriented Architecture ◽  
Lingua Franca ◽  
Enterprise Applications ◽  
Service Oriented ◽  
Restful Web Services ◽  
The Web

The integration of service-oriented architecture (SOA) and grid computing has been gaining momentum since the early 2000s. Most of the SOA-based grid implementations have been created using the lingua franca of the web services, namely SOAP, XML-formatted, message-based services. Although this technology provides advanced features such as security, transactions, reliability and workflow, these features are not always used in grid implementations. Adding these sophisticated features to the technology stack when they are not needed or used makes the implementations difficult and tedious for implementers. Web 2.0 and REST offer a set of techniques and tools that results in a paradigm shift in the web and enterprise applications. This chapter discusses the integration of Web 2.0 and RESTful web services into grid implementations. The suggested techniques and technologies alongside the proposed architecture will be discussed. Moreover, this chapter will explain how this model is useful and greener.

scholarly journals Introduction to Containerization

2020 ◽  
Vol 6 (12) ◽  
pp. 294-300
Author(s):  
Raghav Goel and Dr. Bhoomi Gupta
Keyword(s):  
Large Scale ◽  
Software Engineer ◽  
Service Oriented Architecture ◽  
Use Case ◽  
Production Environment ◽  
Code Base ◽  
Enterprise Applications ◽  
Service Oriented ◽  
Multiple Services ◽  
Local Machine

Are you a software engineer/developer/coder or maybe even a tech enthusiast who is thinking of agility, parallel development and reducing cost. In the early twentieth century, we witnessed the rise of Service Oriented Architecture (SOA), which is a software architecture pattern that allows us to construct large-scale enterprise applications that require us to integrate multiple services, each of which is made over different platforms and languages through a common communication mechanism, where we write code and multiple services talk to each other’s for a business use case, but sometimes we end up with one big monolithic code base whose maintenance becomes difficult. Nowadays clients are using cloud and paying for on-demand services without effectively utilizing resources. These problems invite micro-services. In this paper, I am going to discuss how one should use scale application in a production environment and local machine

Patterns for Migration of SOA Based Applications to Microservices Architecture

2021 ◽  
Author(s):  
Vinay Raj ◽  
Ravichandra Sadam
Keyword(s):  
Programming Languages ◽  
Service Oriented Architecture ◽  
Legacy Systems ◽  
Loose Coupling ◽  
Enterprise Service Bus ◽  
Web Based ◽  
Enterprise Applications ◽  
Service Oriented ◽  
Key Features ◽  
Microservice Architecture

Service oriented architecture (SOA) has been widely used in the design of enterprise applications over the last two decades. Though SOA has become popular in the integration of multiple applications using the enterprise service bus, there are few challenges related to delivery, deployment, governance, and interoperability of services. To overcome the design and maintenance challenges in SOA, a new architecture of microservices has emerged with loose coupling, independent deployment, and scalability as its key features. With the advent of microservices, software architects have started to migrate legacy systems to microservice architecture. However, many challenges arise during the migration of SOA to microservices, including the decomposition of SOA to microservice, the testing of microservices designed using different programming languages, and the monitoring the microservices. In this paper, we aim to provide patterns for the most recurring problems highlighted in the literature i.e, the decomposition of SOA services, the size of each microservice, and the detection of anomalies in microservices. The suggested patterns are combined with our experience in the migration of SOA-based applications to the microservices architecture, and we have also used these patterns in the migration of other SOA applications. We evaluated these patterns with the help of a standard web-based application.

Identifying Services in Procedural Programs for Migrating Legacy System to Service Oriented Architecture

2013 ◽  
pp. 237-255
Author(s):  
Masahide Nakamur ◽  
Hiroshi Igaki ◽  
Takahiro Kimura ◽  
Kenichi Matsumoto
Keyword(s):  
Control System ◽  
Service Oriented Architecture ◽  
Data Flow ◽  
Source Code ◽  
Flow Diagram ◽  
Service Oriented ◽  
Data Flow Diagram ◽  
And Control ◽  
Dependent Processes

In order to support legacy migration to the service-oriented architecture (SOA), this paper presents a pragmatic method that derives candidates of services from procedural programs. In the SOA, every service is supposed to be a process (procedure) with (1) open interface, (2) self-containedness, and (3) coarse granularity for business. Such services are identified from the source code and its data flow diagram (DFD), by analyzing data and control dependencies among processes. Specifically, first the DFD must be obtained with reverse-engineering techniques. For each layer of the DFD, every data flow is classified into three categories. Using the data category and control among procedures, four types of dependency are categorized. Finally, six rules are applied that aggregate mutually dependent processes and extract them as a service. A case study with a liquor shop inventory control system extracts service candidates with various granularities.

Dynamic Reconfiguration of Component-Based Systems

2014 ◽  
pp. 76-102
Author(s):  
Tony Clark ◽  
Balbir S. Barn ◽  
Vinay Kulkarni
Keyword(s):  
Business Processes ◽  
Service Oriented Architecture ◽  
Dynamic Reconfiguration ◽  
System Component ◽  
Ripple Effect ◽  
Dynamic Architecture ◽  
Component Architecture ◽  
Service Oriented ◽  
Typical Component

Component-based approaches generalize basic object-oriented implementations by allowing large collections of objects to be grouped together and externalized in terms of public interfaces. A typical component-based system will include a large number of interacting components. Service-Oriented Architecture (SOA) organizes a system in terms of components that communicate via services. Components publish services that they implement as business processes. Consequently, a change to a single component can have a ripple effect on the service-driven system. Component reconfiguration is motivated by the need to evolve the component architecture and can take a number of forms. The authors define a dynamic architecture as one that supports changing the behavior and topology of existing components without stopping, updating, and redeploying the system. This chapter addresses the problem of dynamic reconfiguration of component-based architectures. It proposes a reification approach that represents key features of a language in data, so that a system can reason and dynamically modify aspects of it. The approach is described in terms of a new language called µLEAP and validated by implementing a simple case study.

Enterprise Integration With the Structural Services Architectural Style

2019 ◽  
pp. 352-392 ◽  
Author(s):  
José Carlos Martins Delgado
Keyword(s):  
Service Oriented Architecture ◽  
Architectural Style ◽  
Enterprise Integration ◽  
Representational State Transfer ◽  
Advantages And Disadvantages ◽  
Architectural Styles ◽  
State Transfer ◽  
Enterprise Applications ◽  
Service Oriented ◽  
Structural Compliance

The Service-Oriented Architecture (SOA) and Representational State Transfer (REST) architectural styles are the most used for the integration of enterprise applications. Each is more adequate to a different class of applications and exhibits advantages and disadvantages. This chapter performs a comparative study between them. It is shown that SOA and REST are dual architectural styles, one oriented towards behavior and the other towards state. This raises the question of whether it is possible to combine them to maximize the advantages and to minimize the disadvantages. A new architectural style, Structural Services, is proposed to obtain the best characteristics from SOA and REST. As in SOA, services are able to offer a variable set of operations and, as in REST, resources are allowed to have structure. This style uses structural interoperability, based on structural compliance and conformance. A service-oriented programming language is also introduced to instantiate this architectural style.

Developing Proactive Security Dimensions for SOA

2011 ◽  
pp. 254-276
Author(s):  
Hany F. EL Yamany ◽  
David S. Allison ◽  
Miriam A.M. Capretz
Keyword(s):  
Service Oriented Architecture ◽  
Security Services ◽  
Security Service ◽  
Service Oriented ◽  
Service Consumer ◽  
Web Services Security ◽  
Soa Security ◽  
Security Standards

Security is one of the largest challenges facing the development of a Service-Oriented Architecture (SOA). This is due to the fact that SOA security is the responsibility of both the service consumer and service provider. In recent years, many solutions have been implemented, such as the Web Services Security Standards, including WS-Security and WS-SecurityPolicy. However, those standards are insufficient for the promising new generations of Web 2.0 applications. In this research, we describe an Intelligent SOA Security (ISOAS) framework and introduce four of its services: Authentication and Security Service (NSS), the Authorization Service (AS), the Privacy Service (PS) and the Service of Quality of Security Service (SQoSS). Furthermore, a case study is presented to examine the behavior of the described security services inside a market SOA environment.

Sign in / Sign up

Export Citation Format

Share Document