Shipping With Context using Knowledge / Context Graphs
Blog post from Harness
AI-generated code faces challenges in software delivery due to a lack of context, not model quality, highlighting the importance of a cohesive system that reflects the interrelationships between various components like pipelines, environments, and policies. Knowledge graphs are proposed as a solution to transform fragmented DevSecOps data into operational truth, emphasizing that overmodeling, undermodeling, and stale context can hinder their effectiveness. AI-assisted DevOps is seen as a preliminary stage where AI helps with tasks like code writing and log summarization, while AI-operational DevOps aims for AI to understand and manage the entire software delivery process. The text argues for the necessity of a shared context layer to allow AI to operate effectively, suggesting that operational reasoning, rather than mere automation, is the goal. The critical role of freshness and relevance in maintaining effective knowledge graphs is stressed, advocating for a focus on minimal, use-case-driven modeling that addresses real-time needs.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| Kubernetes | 13 | 1,840 | 308 | 106 | +33% |
| AI Agents | 5 | 4,545 | 963 | 231 | +27% |
| Observability | 4 | 3,204 | 716 | 172 | +14% |
| Developer Experience | 1 | 482 | 254 | 106 | +18% |
| RAG | 1 | 1,806 | 326 | 91 | +5% |
| Real-time | 1 | 6,457 | 1,307 | 242 | +28% |
| Secrets Management | 1 | 1,488 | 268 | 99 | +7% |