Microservice Architecture Within In-House Infrastructures for Enterprise Integration and Measurement: An Experience Report

Apel, Sebastian; Hertrampf, Florian; Späthe, Steffen

doi:10.1007/978-3-319-93408-2_1

Cited by 5 publications

(5 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…These issues arise from the proprietary descriptors that each service describes, how it is built, how it is packed and baked, and how it is published on target systems. Anyway, our experiences resulting from the development and operation were already published . In addition to that infrastructure requirements, implicit information dependencies emerged as a major reason for the challenges in operation and during development, presented in this paper.…”

Section: Discussionmentioning

confidence: 89%

“…Anyway, our experiences resulting from the development and operation were already published. 4 In addition to that infrastructure requirements, implicit information dependencies emerged as a major reason for the challenges in operation and during development, presented in this paper.…”

Section: Discussionmentioning

confidence: 99%

“…Our microservice architecture is partly realized. As mentioned in our previous publication, there are advantages and disadvantages regarding complexity, modifiability, testability, maintainability, and scalability as well as dependencies. Information irregularities could explain the disadvantages for the areas configuration, endpoints, dependencies, and artefact management.…”

Section: Microservice Setup In Winnermentioning

confidence: 99%

“…The implemented microservice architecture and the outlined experiences 4 indicate difficulties in information management. Several interdependent tools are involved along the supply chain for the publication of services.…”

Section: Service Knowledge Modelmentioning

confidence: 99%

“…Our previous paper 4 outlines experiences in planning, development, deployment, and operation of the WINNER DataLab (WDL). Based on the necessity of in-house operation, this concerns, in particular, the components for a microservice architecture as well as the services for the operation of a compact computing infrastructure and tools to support development and deployment.…”

Section: Introductionmentioning

confidence: 99%

See 4 more Smart Citations

Toward a knowledge model focusing on microservices and cloud computing

Apel

Hertrampf

Späthe

2019

Concurrency and Computation

Self Cite

View full text Add to dashboard Cite

Summary Microservices tend to use a variety of tools to create a well‐defined process of building, packing, backing, and publishing. These tools are usually configured independently by their descriptors. Interrelations between the different tools arise implicitly, but the overall structure only works if the different configurations are correctly coordinated along each other. This paper motivates the development of a knowledge model via a microservice measurement infrastructure within the research project WINNER, which explicitly shapes these interrelationships. For the development of our infrastructure‐related work, experience and requirements of currently common tools are used as a basis. The model contains essential structures for the description of configurations and endpoints, artefacts, and connections for the creation as well as publication process of services result. Our results are applied and discussed in an example.

show abstract

Section: Discussionmentioning

confidence: 89%

Section: Discussionmentioning

confidence: 99%

Section: Microservice Setup In Winnermentioning

confidence: 99%

Section: Service Knowledge Modelmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations