Find research datasets worth reusing
Search datasets from major research repositories and use ShareScore to quickly assess how well each record supports discovery, access, and reuse.
109
datasets available to search
ShareScore release 0.9.0
Dataset results
109 results for “Microservices”
Towards a Process for Migrating Legacy Systems into Microservice Architectural Style
<p>Microservice architectural style is a paradigm to develop systems as a suite of small and autonomous services, communicating thought a light weight protocol. Currently, one of the most common ways of adopting microservice architectures is by the modernization of legacy monolith systems. The migration of a legacy system into a microservice architecture is not a trivial task. In addition, there is a lack of recommendation or guidelines on how to perform such process. In view of this, this paper presents a preliminary process for conducting the migration of legacy systems into microservice architectures. This process was defined by analyzing and discussing pieces of work on the topic. As result, we propose a process composed of eight steps, grouped in four phases, which we describe together with their common input and output.</p>
Multi-faceted Study on Microservices-Based IoT Systems Deployment: Challenges, Practices, and Performance Analysis
Open the record for dataset details and reuse information.
Replication package - Triaging Microservice Security Smells, with TriSS
Open the record for dataset details and reuse information.
Multivocal Study on Microservice Dependencies
Open the record for dataset details and reuse information.
Data Set of From Monolith to Microservices: Static and Dynamic Analysis Comparison
<p>Contains the JSON files with the collected data and the results of the study done.</p>
BARO: Robust Root Cause Analysis for Microservices via Multivariate Bayesian Online Change Point Detection
<p>Artifacts for the paper titled <strong><em>BARO: Robust Root Cause Analysis for Microservices via Multivariate Bayesian Online Change Point Detection</em></strong>.</p> <p>This artifact repository contains 3 compressed folders, as follows: </p> <table> <tbody> <tr> <td><strong>File Name</strong></td> <td><strong>Benchmark System</strong></td> </tr> <tr> <td>fse-ob.zip</td> <td>Online Boutique</td> </tr> <tr> <td>fse-ss.zip</td> <td>Sock Shop</td> </tr> <tr> <td>fse-tt.zip</td> <td>Train Ticket</td> </tr> </tbody> </table> <p>Each zip file contains the collected data from the corresponding microservice benchmark systems (e.g., fse-ob.zip contains metrics data collected from the Online Boutique system). </p> <p><strong><strong>Data description</strong></strong></p> <p>To collect the metrics data, we deploy three benchmark microservice systems: Online Boutique, Sock Shop, and Train Ticket, on a Kubernetes cluster consisting of one master node and five worker nodes. Then, we deploy a monitoring system to monitor and collect resource-level and service-level metrics. To generate traffic, we use the load generators supplied by these systems and tailor them to explore all services with a load of 40-50 requests per second. Initially, we operate the applications normally to gather metrics data under normal conditions. Then, we inject faults into the running services. We execute into the designated container using kubectl exec. For CPU hog and memory leak, we use stress-ng to stress the container resource. For network delay and packet loss, we use tc (traffic control) to manipulate the traffic of the container. Specifically, we inject faults into five targeted services of Sock Shop (carts, catalogue, orders, payment, and user), five targeted services of Online Boutique (adservice, cartservice, checkoutservice, currencyservice, and productcatalogue), and five targeted services of Train Ticket (ts-auth-service, ts-order-service, ts-route-service, ts-train-service, ts-travel-service). For each combination of fault type and targeted service, we repeat the operation (i.e., fault injection and metrics data collection) five times, resulting in 100 failure cases for each benchmark microservice system.</p> <p><strong>Code</strong></p> <p>The code to reproduce the experimental results in the paper is available at <a href="https://github.com/phamquiluan/baro">https://github.com/phamquiluan/baro</a>.</p>
SMS microservices support tools
<p>Form for data extraction, set of extracted papers and data analysis </p>
2D/3D Visualization Study for Microservice Systems
<p>This dataset contains:</p> <ul> <li>The Visualization Models PoC Source Code.</li> <li>Tools' Screenshots.</li> <li>Protocol Material.</li> <li>Study Data Collection and results.</li> </ul>
The supplementary materials for replicating the experiments on Enabling Resilient Production Database Containers for Microservice Applications
Open the record for dataset details and reuse information.
Strategies to mitigate antipatterns in microservices
Open the record for dataset details and reuse information.
The Tale of Errors in Microservices (Artifact part 2)
<p>Part 2 of trace release. Please refer to part 1 <a href="https://doi.org/10.5281/zenodo.13947828">10.5281/zenodo.13947828</a> for details.</p>
Semantic Clones Dataset for TrainTicket Microservices benchmark
<p>It contains Component Call Graphs pairs for the analysis of TrainTicket benchmark (release 0.1.0).</p> <p>It classifies the pairs into semantic clones and non-clones. It contains 27,222 total CCGs pairs.</p> <p>This dataset is published as part of the paper titled as "Detecting Semantic Clones In Microservices Using Components".</p> <p> </p> <p>This version contains correction for 6 pairs are classified as clones. (Highlighted in yellow)</p> <p>This correction is detected using our automatic approach. Check it out in the paper.</p> <p> </p>
Microservice Dependency Matrix: Dataset
<p>This dataset contains the endpoints dependency matrix and data entities dependency matrix extracted from TrainTicket testbench.</p> <p>For more details, checkout the paper titled: The Microservice Dependency Matrix</p>
Micro-Optimisation of Containerised Microservices
<p>Just-for-me configuration for optimising read-only database containers.</p>
Dependency Taxonomy in Microservice Systems
<p>This dataset encompasses the following components:</p> <p>- Data pertaining to the Systematic Literature Review process.</p> <p>- Dependency Artifacts and the corresponding outcomes of the taxonomy process steps.</p>
Scalability Assessment of Microservice Architecture Deployment Configurations: A Domain-based Approach Leveraging Operational Profiles and Load Tests - Reproducibility Package
<p>Reproducibility package for the following publication:</p> <p>Alberto Avritzer, Vincenzo Ferme, Andrea Janes, Barbara Russo, André van Hoorn, Henning Schulz, Daniel Menasché, Vilc Rufino: <em>Scalability Assessment of Microservice Architecture Deployment Configurations: A Domain-based Approach Leveraging Operational Profiles and Load Tests</em>, Journal of Systems and Software, 2020, https://doi.org/10.1016/j.jss.2020.110564.</p>
Industry Practices and Challenges for the Evolvability Assurance of Microservices: A Systematic Grey Literature Review
<p>This repository contains all publicly available artifacts related to a systematic grey literature review (GLR) about the evolvability assurance of microservices in industry. We selected and analyzed 295 practitioner online resources obtained via Google, Bing, and selected StackExchange communities. The study took place in 2020 from January to April.</p>
Applying a Multi-platform Architectural Conformance Solution in a Real-World Microservice-based System
<p>Microservice architectures are composed of a set of independent microservices that execute well-defined functionalities, allowing each one to be developed in different programming languages and data management technologies. The problem, however, is that such heterogeneity implies in a harder verification process of communication among microservices and the architectural designs of each microservice. Thereupon, this paper proposes and evaluates a multiplatform architectural conformance solution for the microservice architecture. For this purpose, (i) we specify an architectural constraint language, called DCL+---adapted from the DCL (Dependency Constraint Language) language; (ii) we propose a multiplatform process that restricts the communication between the microservices and verifies the architectural projects of each one of them; (iii) we develop DCL+check, a tool that implements the proposed solution; (iv) we apply our process in a large real-world application composed of eleven microservices, developed in two different languages (JavaScript and Java). As result, we found 16 communication and 171 structural design violations. The communication violations occurred in general due to the lack of knowledge of the developers about the restrictions of communication among the modules of the orchestrator system and other microservices, as well as the evolution of two microservices. </p>
The Impact of Microservices on the Evolution of a Software Product Line
<p>Video apresentação artigo The Impact of Microservices on the Evolution of a Software Product Line</p>
Evaluating Frameworks Assemblies In Microservices-based Systems Using Imperfect Information (Video)
<p>This video presents a novel technique, called µAzimut, whose purpose is to generate, evaluate, and compare frameworks assemblies using potentially incomplete, imprecise, and changing descriptions of nonfunctional requirements and frameworks. The frameworks assemblies evaluation is based on a support score which allows modeling imperfect architectural knowledge.</p>
ScienceDex guides
Understand access before you commit
These curated guides explain access requirements, typical timelines, costs, and reuse considerations for widely used research datasets.
Allen Brain Atlas
Allen Brain Atlas is an Allen Institute collection of brain map atlases, datasets, APIs, and analysis tools covering mouse, human, and non-human primate brain resources.
Annotated Behaviour and Observability Dataset (ABODe)
ABODe is a University of Edinburgh DataShare dataset for behavior classification in group-housed mice using home-cage video, identities, bounding boxes, ground-plate positions, and annotator labels.
DANDI Archive for NWB datasets
DANDI is a BRAIN Initiative archive for publishing and sharing neurophysiology data, including electrophysiology, optophysiology, and behavioral data packaged as NWB and related standards.
International Brain Laboratory public data
The International Brain Laboratory public data releases expose standardized mouse decision-making experiments, including Neuropixels recordings, widefield calcium imaging, behavior, and session metadata accessed through the ONE API.
OpenNeuro
OpenNeuro is a free, open platform for sharing neuroimaging datasets, with public search, dataset pages, and download paths for web, S3, DataLad, and the OpenNeuro CLI.