@conference {2021:plop,
	title = {Patterns on Designing API Endpoint Operations},
	booktitle = {28th Conference on Pattern Languages of Programs (PLoP{\textquoteright}21)},
	year = {2021},
	month = {October},
	publisher = {ACM},
	organization = {ACM},
	address = {Virtual},
	abstract = {Domain-driven design (DDD) is often applied when implementing microservices or communicating through APIs in distributed
systems. APIs expose a published language that provides a view on entire domain models or subsets of such models. Hence,
tactical DDD patterns such as Aggregate, Service, and Entity may not only structure API implementations, but also guide API
specification work. In our previous work, we described endpoint-level patterns for this context. In this paper, we present three
complementary patterns, namely Aggregated Domain Operation on API Endpoint, Event-Based API Endpoint Operation, and
CRUD-Based API Operation. These patterns aim to derive API operations from the operations of Domain Services and Entities
as well as Domain Events. We also discuss variants of these patterns, such as their combination with the patterns Command
Query Responsibility Segregation (CQRS) and Publish/Subscribe. Our pattern mining work is based on a data set from an
empirical study of 32 grey literature sources investigating practitioner views on deriving API designs from DDD models.},
	keywords = {API, Domain-Driven Design},
	author = {Apitchaka Singjai and Uwe Zdun and Olaf Zimmermann and Mirko Stocker and Cesare Pautasso}
}
@conference {2018:map:icsoc,
	title = {Guiding Architectural Decision Making on Quality Aspects of Microservice APIs},
	booktitle = {16th International Conference on Service-Oriented Computing (ICSOC 2018)},
	volume = {11236},
	year = {2018},
	month = {November},
	pages = {73-89},
	publisher = {Springer},
	organization = {Springer},
	address = {Hangzhou, Zhejiang, China},
	abstract = {Microservice APIs represent the client perspective on microservice-based software architecture design and related practices. Major issues in API design concern the quality aspects of the API. However, it is not well understood today what the established practices related to those quality aspects are, how these practices are related, and what the major decision drivers are. This leads to great uncertainty in the design process. In this paper, we report on a qualitative, in-depth study of 31 widely used APIs plus 24 API specifications, standards, and technologies. In our study we identified six recurring architectural design decisions in two API design contexts with a total of 40 decision options and a total of 47 decision drivers. We modelled our findings in a formal, reusable architectural decision model. We measured the uncertainty in the resulting design space with and without use of our model, and found that a substantial uncertainty reduction can be potentially achieved by applying our model.
},
	keywords = {API, Microservices, quality},
	doi = {10.1007/978-3-030-03596-9_5},
	author = {Uwe Zdun and Mirko Stocker and Olaf Zimmermann and Cesare Pautasso and Daniel L{\"u}bke}
}
