scholarly journals Microservices Software Architecture: A Review

2021 ◽  
Vol 9 (11) ◽  
pp. 1494-1496
Author(s):  
Chitrak Vimalbhai Dave
Keyword(s):  
Software Engineering ◽  
Software Architecture ◽  
Service Oriented Architecture ◽  
Organizational Values ◽  
Software Applications ◽  
Service Oriented ◽  
Design Software ◽  
Infrastructural Support

Abstract: Architecting is an indispensable activity in all spheres and paradigms of Software Engineering. DevOps, a portmanteau of Development and Operations, has a major adoption challenge in context to Microservices Architecture. Architecture refers to the most important aspect of internal design of a software. Architecture must be good otherwise; it will become slow and much more expensive to add new proficiencies in future. This paper has presented a review of microservices architecture and implementation patterns. Microservice approach is a new concept in software architecture patterns and has leapt up over past few years for describing a certain method to design software applications as collections of individualistically deployable services. In this paper we are looking to discover the role of microservices software architecture in DevOps. It is found that adopting DevOps may carry many challenges/issues like organizational values, immaturity of the tools and infrastructural support with it for architecting with it. Keywords: Microservices Architecture, Microservice, Service Oriented Architecture (SOA), Software Architecture, DevOps

A Role of Enterprise Service Bus in Building Web Services

2017 ◽  
pp. 46-58
Author(s):  
Dinesh Sharma ◽  
Devendra Kumar Mishra
Keyword(s):  
Web Services ◽  
Business Processes ◽  
Service Oriented Architecture ◽  
Enterprise Service Bus ◽  
Fast Processing ◽  
Service Oriented ◽  
Open Standards ◽  
Or Organization ◽  
Services Use

Present is the era of fast processing industries or organization gives more emphasis for planning of business processes. This planning may differ from industry to industry. Service oriented architecture provides extensible and simple architecture for industry problem solutions. Web services are a standardized way for developing interoperable applications. Web services use open standards and protocols like http, xml and soap. This chapter provides a role of enterprise service bus in building web services.

Semi-Automated Lifecycles for Eliciting Requirements for Service-Oriented Environments

2013 ◽  
pp. 22-34
Author(s):  
M. Brian Blake
Keyword(s):  
Software Engineering ◽  
Requirements Engineering ◽  
Service Oriented Architecture ◽  
Future Application ◽  
Service Oriented Architectures ◽  
Requirements Specifications ◽  
Business Information ◽  
Service Oriented ◽  
Enterprise Modernization ◽  
Development Applications

Service-based tools are beginning to mature, but there is a cognitive gap between the understanding of what currently exists within an organization and how to use that knowledge in planning an overall enterprise modernization effort that realizes a service-oriented architecture. Traditional and contemporary software engineering lifecycles use incremental approaches to extract business information from stakeholders in developing features and constraints in a future application. In traditional environments, this information is captured as requirements specifications, use cases, or storyboards. Here, we address the evolution of traditional software engineering approaches to support the conceptualization of abstract services that overlap multiple organizations. Traditional software engineering lifecycles must be enhanced with emerging processes related to the development applications for service-oriented environments. The chapter discusses state-of-the-art approaches that elicit information about the requirements for service-oriented architectures. These approaches tend to leverage existing requirements engineering approaches to suggest aggregate service-based capabilities that might be most effective for a particular environment.

Advanced Technologies and Architecture for Collaborative Business

2010 ◽  
pp. 121-150
Author(s):  
Bhuvan Unhelkar ◽  
Abbass Ghanbary ◽  
Houman Younessi
Keyword(s):  
Business Processes ◽  
Service Oriented Architecture ◽  
Business Environment ◽  
Process Engineering ◽  
System Architectures ◽  
Service Oriented ◽  
Technical Collaboration ◽  
Role Of Information ◽  
Technical Platform

This chapter discusses the role of information system architectures in Collaborate Business Process Engineering (CBPE). Thus, in this chapter, there is an extension of the discussion on Service-oriented Architecture (SOA) from chapters 2 and 4, and its importance and relevance to CBPE. The SOA based architecture is extended and applied in a collaborative business environment. The technical platform of Service Oriented Architecture (SOA) provides an ideal mechanism to start building collaborative business processes, as it facilitates technical collaboration of different environments - as discussed in this chapter.

Service-Oriented Architectures for Pervasive Computing

2010 ◽  
pp. 147-174 ◽  
Author(s):  
Elias S. Manolakos ◽  
Demetris G. Galatopoullos
Keyword(s):  
Pervasive Computing ◽  
Service Oriented Architecture ◽  
Future Research ◽  
Open Problems ◽  
Efficient Manner ◽  
Service Oriented Architectures ◽  
Software Applications ◽  
Service Oriented ◽  
User Tasks ◽  
The Many

The vision of pervasive computing is to create and manage computational spaces where large numbers of heterogeneous devices collaborate transparently to serve the user tasks all the time, anywhere. The original utility of a computer is now changing from a stand-alone tool that runs software applications to an environment-aware, context-aware tool that can enhance the user experience by executing services and carrying out his/her tasks in an efficient manner. However, the heterogeneity of devices and the user’s mobility are among the many issues that make developing pervasive computing applications a very challenging task. A solution to the programmability of pervasive spaces is adopting the service-oriented architecture (SOA) paradigm. In the SOA model, device capabilities are exposed as software services thus providing the programmer with a convenient abstraction level that can help to deal with the dynamicity of pervasive spaces. In this chapter the authors review the state of the art in SOA-based pervasive computing, identify existing open problems, and contribute ideas for future research.

Transitioning Business Processes to a Collaborative Business Environment with Mobility

2009 ◽  
pp. 73-82
Author(s):  
Bhuvan Unhelkar ◽  
Amit Tiwary ◽  
Abbass Ghanbary
Keyword(s):  
Web Services ◽  
Enterprise Architecture ◽  
Business Processes ◽  
Service Oriented Architecture ◽  
Business Environment ◽  
Web Based ◽  
Software Applications ◽  
Comprehensive Service ◽  
Service Oriented ◽  
Web Based System

Web Services (WS) technologies create the potential for an organization to collaborate with partners and customers by enabling its software applications to transact over the Internet. This collaboration is achieved by carefully incorporating Web Services in the organization’s software applications, resulting in comprehensive Service-Oriented Architecture (SOA) for the enterprise. This incorporation of WS-enabled applications and components in the organization’s overall enterprise architecture requires understanding of the service at three interrelated yet distinct layers: policies, activities, and standards. This chapter describes how the existing business processes of an organization are transitioned in to collaborative business processes that would result in a Collaborative Web- Based System (CWBS). The ideas presented in this chapter have been validated through an action-research carried out by the authors in a large energy supplier organization in Melbourne, Australia.

A Comparative Analysis of Reliability Assessment Methods for Web-Based Software

2013 ◽  
Vol 1 (4) ◽  
pp. 31-44 ◽  
Author(s):  
Jinhee Park ◽  
Yeong-Seok Seo ◽  
Jongmoon Baik
Keyword(s):  
Service Oriented Architecture ◽  
Reliability Assessment ◽  
Dynamic Environment ◽  
Assessment Methods ◽  
Software Systems ◽  
Web Based ◽  
Software Applications ◽  
Web Environment ◽  
Service Oriented ◽  
The Web

As web technology has advanced, many business software applications are built on the web. In such web environment, it has become very important to ensure the reliabilities of web-based software systems such as Software as a Service (SaaS) or Service-Oriented Architecture (SOA) based systems because service failures in those systems may have an effect on extensive users. With the comparison to the reliability studies on traditional software, there are only a few studies on the reliability of web-based software. The dynamic environment of the web makes it much more complicated to assess the reliabilities of web-based software. In this paper, the authors investigate the characteristics of reliability assessment methods for web-based software such as SaaS and SOA based software systems. The authors also evaluate those methods based on hypothetical execution scenarios to analyze the strengths and weaknesses of each method. This analysis helps us to identify remaining problems on the reliability research in the web environment and provides insight into possible solutions.

A Review of Software Architecture for Collaborative Software’s

2012 ◽  
Vol 433-440 ◽  
pp. 2372-2376 ◽  
Author(s):  
Mehdi Bahrami ◽  
Mohammad Bahrami
Keyword(s):  
Software Engineering ◽  
Software Architecture ◽  
System Application ◽  
Development Process ◽  
System Development ◽  
Shared Understanding ◽  
Collaborative Systems ◽  
Future Directions ◽  
Software Application ◽  
Software Applications

Software architecture has emerged as an important sub-discipline of software engineering; particularly in the realm of large system development. Collaboration software applications are inherently cooperative, requiring many software applications to coordinate their efforts to produce a software system application. Integral to this effort is developing shared understanding surrounding multiple artifacts, each artifact embodying its own model, over the entire development process. This focus on model collaboration embedded within a larger process is what distinguishes collaboration research in software engineering from broader collaboration research. This article first review a list of goals for software architecture, then collaboration software application, several possible future directions for collaboration in software engineering is presented. The article concludes by noting a problem in performing research on collaborative systems.

Sign in / Sign up

Export Citation Format

Share Document