Using Gremlin.NET and Azure Cosmos DB for code analysis
summary
A .NET code-analysis pipeline stores a property-graph model of assemblies in Azure Cosmos DB using Gremlin.NET and a custom bytecode-to-script translator that turns TinkerPop bytecode into Cosmos-compatible Gremlin strings. The prototype deserializes vertices, edges, paths and valueMaps, runs queries (for example classes with >30 incoming edges) and visualizes coupling; it currently analyzes standard .NET Framework assemblies and persists results to Cosmos DB. Work in progress lives at bytecode4cosmosdb on GitHub.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 2:00Motivation
- 3:40Persistence
- 5:13Gremlin
- 6:18Property Graph
- 7:34Code Model to Graph
- 9:15Gremlin NET
- 10:22Cosmos DB Connection
- 12:45Submitting the query
- 13:43Drawbacks
- 14:34Bitcode based requests
- 15:04GremlinNET extensions
- 15:40bytecode based request
- 17:38what now
- 18:10bytecode based approach
- 19:07driver remote connection
- 19:50driver remote connection interface
- 20:25current implementation
- 20:50Groovy translator
- 21:01Deserialization
- 22:12Analyzing NET assemblies
- 22:31Querying data
- 23:33Voided method
- 24:19Conclusion
related talks
57mGraphing Your Way Through the Cosmos: Common Data Problems Solved with Graphs
45mGetting the Most from NoSQL in the Cloud with Azure Cosmos DB
37mType safety in the world of graph databases
47mWorking with data using Azure Functions
02mRecap
12mBuilding Generative AI Apps with Azure Cosmos DB
54mSay Yes to NoSQL for the .NET SQL Developer
50mAnalyzing Code in .NET