alibaba / alibaba/clusterdata

Determining Stateless vs Stateful Microservices in MSCallGraph in MicroserviceTrace-v2021

Open
#160 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Jupyter Notebook
Stars
2.2k
Forks
482
PR merge metrics
No merged PRs in 30d

Description

How do we distinguish between stateless and stateful microservices in MicroserviceTrace-v2021? I noticed that the descriptions of MS_MCR_RT_Table and MS_Metrics_Table both explicitly say that all msnames in the tables represent stateless services. However, it seems like these two tables are not available to be downloaded as they are not in the four tables listed here.
![Screen Shot 2022-11-15 at 09 24 52](https://user-images.githubusercontent.com/20631215/201985791-fbb74e9e-9aa3-4733-a18f-318c44791412.png)
Additionally, the description of MSCallGraph does not mention anything about only including stateless microservices. I have two questions:
1. Are the microservices (um and dm) in MSCallGraph all stateless or are they a combination of stateless and stateful services?
2. If they are a combination of both, is there some way to distinguish between stateless and stateful microservices in the MSCallGraph table?

Contributor guide

No contributing guide indexed for this repository

Research direction

Review the MicroserviceTrace-v2021 documentation for MSCallGraph, MS_MCR_RT_Table, MS_Metrics_Table, and the four listed downloadable tables. Determine whether um and dm are stateless or stateful and whether the MSCallGraph table exposes a distinguishing field; done means the documentation clearly answers both questions.

Written by the indexing model from the issue text.

Assessment

Domain
data, documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.