MOBIUSI INCThis dataset collects source code implementations for handling request contexts, trace identifiers, and cross-service metadata across multiple programming languages and frameworks. It covers common service boundaries, including HTTP, RPC, messaging, and service mesh integrations, with structured annotations for languages, frameworks, context APIs, metadata carriers, and propagation stages. It supports coding agent training and evaluation, distributed tracing analysis, and code understanding and generation for microservice context propagation.
| Field | Type | Description |
|---|---|---|
| file_name | string | File name |
| framework | string | The primary application framework, RPC framework, service mesh component, or client library identified in the source code. |
| code_summary | string | An English summary of the context creation, extraction, injection, forwarding, and restoration logic in the source code. |
| source_artifact | object | The source code to be analyzed and its original file metadata. |
| context_api_names | array | Names of APIs, classes, functions, or methods used to create, read, modify, or pass request context in the code. |
| metadata_carriers | array | Carriers used to propagate context metadata across threads, processes, or services, such as request headers, RPC metadata, message attributes, or environment variables. |
| propagation_stages | array | Context propagation stages represented in the code, such as inbound extraction, context injection, client calls, or server-side restoration. |
| propagation_pattern | string | The context propagation pattern inferred from the code, such as explicit parameter passing, implicit thread context, header injection, or automatic service mesh injection. |
| programming_language | string | The primary programming language identified in the source code. |
| service_boundary_types | array | Types of service boundaries crossed by the code, such as HTTP, gRPC, message queues, database calls, or service mesh proxies. |
| trace_identifier_types | array | Types of trace identifiers propagated or extracted in the code, such as trace_id, span_id, or request correlation identifiers. |
| supports_cross_service_propagation | boolean | Whether the source code can propagate request context, trace identifiers, or related metadata to other services. |
| Authorization Type | Proprietary - Commercial AI Training License (No Redistribution) |
| Commercial Use | Requires exclusive subscription or authorization contract (monthly or per-invocation charging) |
| Privacy and Anonymization | No PII, no real company names, simulated scenarios follow industry standards |
| Compliance System | Compliant with China's Data Security Law / EU GDPR / supports enterprise data access logs |

Post a request and let data providers reach out to you.
@dataset{Mobiusi2026,
title={Distributed Context Propagation Code Dataset},
author={MOBIUSI INC},
year={2026},
url={https://www.mobiusi.com/datasets/447fcba3d8811f00ab487d93d9557fb7},
urldate={2026-10-14},
keywords={distributed context propagation,microservice code dataset,distributed tracing code,request context propagation,service mesh code,cross-service metadata,coding agent training,source code understanding},
version={1.0}
}Using this in research? Please cite us.