Let's Have a Conversation

Hohpe, Gregor

doi:10.1109/mic.2007.68

Cited by 15 publications

(6 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Regarding computations performed across microservices, conversations (i.e., the interaction between a set of consumer and provider services) are prevalent. Hohpe [34] argues that orchestration and choreography are the two types of conversations that take place in the context of distributed web applications. Most papers [4,31,42,43,49,50,66] and open-source projects [3,19,38,52,69,70,72,81] report the use of the choreography conversation pattern [34] through both synchronous workflows and asynchronous event-based workflows.…”

Section: Business Transactions Across Microservicesmentioning

confidence: 99%

Data Management in Microservices: State of the Practice, Challenges, and Research Directions

Laigner,

Zhou,

Salles

et al. 2021

Preprint

View full text Add to dashboard Cite

We are recently witnessing an increased adoption of microservice architectures by the industry for achieving scalability by functional decomposition, fault-tolerance by deployment of small and independent services, and polyglot persistence by the adoption of different database technologies specific to the needs of each service. Despite the accelerating industrial adoption and the extensive research on microservices, there is a lack of thorough investigation on the state of the practice and the major challenges faced by practitioners with regard to data management.To bridge this gap, this paper presents a detailed investigation of data management in microservices. Our exploratory study is based on the following methodology: (i) we conducted a systematic literature review of articles reporting the adoption of microservices in industry settings, where more than 300 articles were filtered down to 11 representative studies; (ii) we analyzed a set of 9 popular open-source microservice-based applications, selected out of more than 20 open-source projects; furthermore, (iii) to strengthen our evidence, we conducted an online survey that we then used to crossvalidate the findings of the previous steps with the perceptions and experiences of over 120 practitioners and researchers.Through this process, we were able to categorize the state of practice and reveal several principled challenges that cannot be solved by software engineering practices, but rather need systemlevel support to alleviate the burden of practitioners. Based on the observations we also identified a series of research directions to achieve this goal. Fundamentally, novel database systems and data management tools that support isolation for microservices, which include fault isolation, performance isolation, data ownership, and independent schema evolution across microservices must be built to address the needs of this growing architectural style.

show abstract

Section: Business Transactions Across Microservicesmentioning

confidence: 99%

Data Management in Microservices: State of the Practice, Challenges, and Research Directions

Laigner,

Zhou,

Salles

et al. 2021

Preprint

View full text Add to dashboard Cite

show abstract

“…The importance of conversations and the need for services to describe the supported conversation types was originally discussed in the context of messaging middleware [40]. RESTful conversation is a well-known concept in service design to describe interactions between a client and one or multiple resources.…”

Section: Restful Conversationmentioning

confidence: 99%

Data Service API Design for Data Analytics

Yun

Zhu

et al. 2018

Services Computing – SCC 2018

View full text Add to dashboard Cite

show abstract

“…Thanks to hypermedia and the uniform interface (e.g., idempotent receiver semantics are implicitly given), applying conversations to REST gives an elegant solution to some of the conversation description challenges identified by [17], where the importance of conversations and the need for services to describe the supported conversation types was originally discussed in the context of messaging middleware. A good starting point showing how conversations were introduced for traditional WSDL-based services is [18], where the authors develop the concept starting from a survey of e-commerce Web portals, which were however analyzed abstracting away the underlying HTTP interactions.…”

Section: Related Workmentioning

confidence: 99%

A Conversation Based Approach for Modeling REST APIs

Haupt

Leymann

Pautasso

2015

2015 12th Working IEEE/IFIP Conference on Software Architecture

View full text Add to dashboard Cite

Abstract-Conversations are a well-known concept in service design to describe complex interactions between a client and one or multiple services. The REST architectural style constrains the characteristics of clients, servers and their interactions in REST architectures which consequently has an impact on conversations in such systems. The relation between conversations and REST architectures and how such RESTful conversations can be characterized has not been studied in detail yet. In this paper we discuss the characteristics of conversations in REST architectures and introduce an initial set of commonly used conversation types. Based on this, we propose to use conversations as a modeling tool for the design of REST APIs at a higher level of abstraction. We also introduce a corresponding interaction centric metamodel for REST APIs. The characterization of RESTful conversations enables a new interaction centric viewpoint on REST architectures which can be also applied for modeling REST APIs on an abstraction level that enables users to focus on the essential functionality of their REST API.

show abstract

Let's Have a Conversation

Cited by 15 publications

References 0 publications

Data Management in Microservices: State of the Practice, Challenges, and Research Directions

Data Management in Microservices: State of the Practice, Challenges, and Research Directions

Data Service API Design for Data Analytics

A Conversation Based Approach for Modeling REST APIs

Contact Info

Product

Resources

About