Why Do We Need an Agent Framework? • Rod Johnson • YOW! 2025

Why Do We Need an Agent Framework? • Rod Johnson • YOW! 2025

🎙 Rod Johnson 👥 1.1M 📅 June 5, 2026 ⏱ 44 min 👁 1K 📄 expert opinion 🧭 2026-08-02
Available in: English (current) Français

Keywords

agent frameworkenterprise GenAInon-determinismorchestrationstructured output

Summary

Rod Johnson, founder of SpringSource, presents a talk at YOW! 2025 on the necessity of agent frameworks for enterprise GenAI. He contrasts the success of personal productivity tools like coding assistants with the failures of enterprise GenAI projects, attributing the latter to non-determinism, prompt engineering’s alchemy-like nature, and organizational issues like top-down mandates and siloed teams. He argues that orchestration is essential, but step planning must be deterministic, unlike approaches that rely on LLMs for planning. He advocates for breaking large tasks into smaller, structured steps that return structured data (e.g., records, data classes) rather than free text, enabling validation and guardrails with traditional code. He emphasizes integrating with existing enterprise systems, being incremental, and using domain expertise. He introduces ‘domain integrated context engineering’ as an improvement over prompt engineering. The talk includes a demo of Embabel, his open-source agent framework for the JVM, and concludes with a Q&A.

149 words

Critical Evaluation

Rod Johnson’s talk provides a pragmatic and insightful analysis of why enterprise GenAI projects often fail and what can be done to improve their success rate. His central thesis is that the non-deterministic nature of LLMs is the fundamental challenge, and that orchestration with deterministic step planning is the key to mitigating this. This argument is well-articulated and supported by real-world examples, such as the Air Canada chatbot incident, which illustrates the consequences of uncontrolled AI behavior in customer-facing processes. Johnson’s distinction between personal productivity tools, where human oversight can correct errors, and business processes, where such oversight is not always feasible, is a crucial insight that is often overlooked in the hype surrounding GenAI. He also rightly criticizes the term ‘prompt engineering’ as misleading, proposing ‘context engineering’ instead, which emphasizes the importance of providing the right context to the model. His advocacy for structured outputs over free text is technically sound, as it enables deterministic validation and integration with traditional code, a point that aligns with best practices in software engineering. The organizational challenges he identifies, such as top-down mandates and siloed teams, are well-known but often ignored; his anecdote about a Python-focused AI team unaware of their company’s Java stack highlights a common disconnect. However, the talk is not without limitations. Johnson’s claims about the failure rates of enterprise GenAI projects are based on surveys he admits may not be fully valid, and he does not provide specific data or citations to support his assertions. The demo of Embabel is brief and may not fully convince viewers of its superiority over existing frameworks. Additionally, while he mentions LangGraph, CrewAI, and Imbue as examples of deterministic orchestration frameworks, he does not provide a detailed comparison or evaluation. The talk is primarily an opinion piece based on his extensive experience, which lends it credibility, but it lacks the rigor of a systematic study. The title is well-aligned with the content, as Johnson thoroughly addresses the need for agent frameworks and why another one (Embabel) is justified. Overall, the talk offers valuable insights for practitioners, but its arguments would benefit from more empirical evidence and a more detailed technical analysis.

359 words

Title / Content Match

The title accurately reflects the talk's focus on the necessity of agent frameworks for enterprise GenAI, addressing both the 'why' and the 'why another'.

Quality & Reliability

7/10

Rod Johnson, founder of SpringSource, provides a pragmatic, experience-based perspective on enterprise GenAI challenges. He identifies key issues like non-determinism and organizational pitfalls, and advocates for deterministic orchestration and structured outputs. While not a formal study, his arguments are coherent and grounded in real-world examples, though some claims lack empirical backing.

Chapters

Cited Sources

Concurring Sources

  • LangGraph — Mentioned as an example of deterministic orchestration framework.
  • CrewAI — Mentioned as an example of deterministic orchestration framework.

Dissenting Sources

External References

Contribution & Novelties

The talk provides a clear framework for understanding the challenges of enterprise GenAI and argues for a deterministic orchestration approach, which is a valuable perspective. It introduces the concept of ‘domain integrated context engineering’ as an improvement over prompt engineering. The presentation of Embabel, a new open-source agent framework for the JVM, offers a concrete solution for Java/Kotlin developers.

Pour aller plus loin :

  • LangGraph — A framework for building stateful, multi-agent applications with deterministic control flow.
  • CrewAI — A Python framework for orchestrating role-playing autonomous AI agents.
  • Microsoft Semantic Kernel — An SDK that integrates LLMs into applications, offering orchestration capabilities.
  • Model Context Protocol (MCP) — An open protocol for connecting AI models to external tools and data sources.
  • Air Canada chatbot incident — A notable example of a GenAI failure in customer service, illustrating the risks of non-deterministic systems.

141 words

Radar Profile

The radar profile shows a balanced distribution across information quantity, quality, technical level, and reliability, with a slight emphasis on quantity and reliability. This indicates a talk that provides substantial content with a strong practical orientation, though it may not delve deeply into technical specifics.

Reliability 7/10