Companion Proceedings of The10th International Conference on Utility and Cloud Computing 2017
DOI: 10.1145/3147234.3148093
|View full text |Cite
|
Sign up to set email alerts
|

Microservices

Abstract: Microservice Architectures (MA) have the potential to increase the agility of software development. In an era where businesses require software applications to evolve to support emerging software requirements, particularly for Internet of Things (IoT) applications, we examine the issue of microservice granularity and explore its effect upon application latency. Two approaches to microservice deployment are simulated; the first with microservices in a single container, and the second with microservices partitio… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
5
0

Year Published

2019
2019
2024
2024

Publication Types

Select...
4
3
1
1

Relationship

0
9

Authors

Journals

citations
Cited by 29 publications
(6 citation statements)
references
References 13 publications
0
5
0
Order By: Relevance
“…Granularity: The functional scope or size of a microservice is generally referred to as the microservice granularity (Shadija et al 2017). Granularity can be mathematically represented by the ratio between the original system size and the total number of microservices in the decomposition (Driessen Famkeand Ferreira Pires 2024).…”
Section: Software Quality Properties For Maintainabilitymentioning
confidence: 99%
“…Granularity: The functional scope or size of a microservice is generally referred to as the microservice granularity (Shadija et al 2017). Granularity can be mathematically represented by the ratio between the original system size and the total number of microservices in the decomposition (Driessen Famkeand Ferreira Pires 2024).…”
Section: Software Quality Properties For Maintainabilitymentioning
confidence: 99%
“…A microservice implements and supports a dedicated business capability which is normally comprised of several functionalities coupled in a service [68,202]. How big or small microservices should be is an ongoing debate [245,265]. However, when services are designed to only provide a single functionality -as is the case with FaaS -then the size should be even smaller.…”
Section: Related Technologiesmentioning
confidence: 99%
“…[18], [19], [20], [21], [22], [23], [24], [25], [26], [27], [28], [29]. [36], [37], [38], [39], [40], [41], [42] Performance. Scalability.…”
Section: Related Workmentioning
confidence: 99%