Service-oriented architecture for big data and business intelligence analytics in the cloud

© 2017 by Taylor & Francis Group, LLC. Service-oriented architecture (SOA) has emerged, supporting scalability and service reuse. At the same time, Big Data analytics has impacted on business services and business process management. However, there is a lack of a systematic engineering approach to Big Data analytics. This chapter provides a systematic approach to SOA design strategies and business process for Big Data analytics. Our approach is based on SOA reference architecture and service component model for Big Data applications, known as softBD and also includes a large-scale, real-world case study demonstrating our approach to SOA for Big Data analytics. SOA Big Data architecture is scalable, generic, and customizable for a variety of data applications. The main contribution of this chapter includes a unique, innovative, and generic softBD framework, service component model, and a generic SOA architecture for large-scale Big Data applications. This chapter also contributes to Big Data metrics, which allows measurement and evaluation when analyzing data

A Framework for the Design of Service Maps

The concept of service-oriented architecture (SOA) is recognized as an important enabler for business transformation and application integration. Service maps emerge when individual services are (pre)configured on various architectural levels. For example, business-oriented service maps sustain the communication and coordination among participants within and between businesses. Difficulties occur when, based on different service design strategies, heterogeneous service maps are created which need to be aligned. A methodological approach to establish a systematic design process for such service maps within companies or business networks is needed

Exploring Maintainability Assurance Research for Service- and Microservice-Based Systems: Directions and Differences

To ensure sustainable software maintenance and evolution, a diverse set of activities and concepts like metrics, change impact analysis, or antipattern detection can be used. Special maintainability assurance techniques have been proposed for service- and microservice-based systems, but it is difficult to get a comprehensive overview of this publication landscape. We therefore conducted a systematic literature review (SLR) to collect and categorize maintainability assurance approaches for service-oriented architecture (SOA) and microservices. Our search strategy led to the selection of 223 primary studies from 2007 to 2018 which we categorized with a threefold taxonomy: a) architectural (SOA, microservices, both), b) methodical (method or contribution of the study), and c) thematic (maintainability assurance subfield). We discuss the distribution among these categories and present different research directions as well as exemplary studies per thematic category. The primary finding of our SLR is that, while very few approaches have been suggested for microservices so far (24 of 223, ?11%), we identified several thematic categories where existing SOA techniques could be adapted for the maintainability assurance of microservices

A Systematic Method for Identification of Anti-patterns in Service Oriented System Development

Service-Oriented Architecture is one of the popular software architecture's patterns used for developing lots of modern systems. However, it has been involved in many failures. Anti-patterns are solutions which have good view, but in fact they are wrong solutions that cause failure of systems. There are a lot of anti-patterns for SOA and new anti-patterns are revealed every day. Anti-patterns have their own reasons for being formed and also they are appeared in special area of the problem. As human's mind is restricted and it can process a limited number of states (piece of information) therefore identification of anti-patterns will be difficult for architects. In this paper, we propose a systematic method based on repository of anti-patterns along with a check list to identify anti-patterns of SOA. This method will assist architects to easily detect and avoid anti-patterns in development process and so escape from risks which related to anti-patterns. Furthermore, in this paper, we present a repository of forty five general anti-patterns in SOA. Reviewing these anti-patterns will help developers to work with clear understanding of patterns in phases of software development and so avoid from many potential problems. Also, our method is evaluated in action.DOI:http://dx.doi.org/10.11591/ijece.v4i1.409

Service architecture design for E-Businesses: A pattern-based approach

E-business involves the implementation of business processes over the Web. At a technical level, this imposes an application integration problem. In a wider sense, the integration of software and business levels across organisations becomes a significant challenge. Service architectures are an increasingly adopted architectural approach for solving Enterprise Applications Integration (EAI). The adoption of this new architectural paradigm requires adaptation or creation of novel methodologies and techniques to solve the integration problem. In this paper we present the pattern-based techniques supporting a methodological framework to design service architectures for EAI. The techniques are used for services identification, for transformation from business models to service architectures and for architecture modifications

Microservice Transition and its Granularity Problem: A Systematic Mapping Study

Microservices have gained wide recognition and acceptance in software industries as an emerging architectural style for autonomic, scalable, and more reliable computing. The transition to microservices has been highly motivated by the need for better alignment of technical design decisions with improving value potentials of architectures. Despite microservices' popularity, research still lacks disciplined understanding of transition and consensus on the principles and activities underlying "micro-ing" architectures. In this paper, we report on a systematic mapping study that consolidates various views, approaches and activities that commonly assist in the transition to microservices. The study aims to provide a better understanding of the transition; it also contributes a working definition of the transition and technical activities underlying it. We term the transition and technical activities leading to microservice architectures as microservitization. We then shed light on a fundamental problem of microservitization: microservice granularity and reasoning about its adaptation as first-class entities. This study reviews state-of-the-art and -practice related to reasoning about microservice granularity; it reviews modelling approaches, aspects considered, guidelines and processes used to reason about microservice granularity. This study identifies opportunities for future research and development related to reasoning about microservice granularity.Comment: 36 pages including references, 6 figures, and 3 table

Towards a service-oriented e-infrastructure for multidisciplinary environmental research

Research e-infrastructures are considered to have generic and thematic parts. The generic part provids high-speed networks, grid (large-scale distributed computing) and database systems (digital repositories and data transfer systems) applicable to all research commnities irrespective of discipline. Thematic parts are specific deployments of e-infrastructures to support diverse virtual research communities. The needs of a virtual community of multidisciplinary envronmental researchers are yet to be investigated. We envisage and argue for an e-infrastructure that will enable environmental researchers to develop environmental models and software entirely out of existing components through loose coupling of diverse digital resources based on the service-oriented achitecture. We discuss four specific aspects for consideration for a future e-infrastructure: 1) provision of digital resources (data, models & tools) as web services, 2) dealing with stateless and non-transactional nature of web services using workflow management systems, 3) enabling web servce discovery, composition and orchestration through semantic registries, and 4) creating synergy with existing grid infrastructures