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

· Source: GOTO Conferences · Field: Technology & Digital — Artificial Intelligence & Machine Learning, Software Development & Engineering, Emerging Technologies & Innovation · Depth: Advanced, extended

Summary

Rod Johnson's YOW! 2025 talk highlights the disparity between GenAI's success in personal productivity and its struggles in enterprise business processes. While coding agents benefit from user intervention and "git revert" capabilities, enterprise applications lack this fault tolerance for customer interactions, as seen in the Air Canada chatbot case. Enterprise GenAI projects frequently fail due to inherent non-determinism, "prompt engineering as alchemy," and performance costs, alongside organizational issues like top-down mandates and siloed teams. Johnson advocates for breaking down large tasks into deterministic, structured steps, integrating with existing systems, and applying "domain integrated context engineering" that leverages established domain models. He introduces Embabel, a new JVM framework built on Spring, designed to maximize determinism, facilitate integration, emphasize domain modeling, and enable type-safe mixing of code with LLM operations, supporting various models and using GOAP for predictable planning.

Key takeaway

For AI Engineers or Architects building enterprise GenAI applications, you must prioritize deterministic orchestration and structured data exchanges over "god model" approaches. Focus on integrating GenAI with existing JVM systems and domain models to achieve predictability and testability. This strategy, exemplified by frameworks like Embabel, mitigates risks of non-deterministic, text-only outputs and ensures robust, maintainable solutions, avoiding common enterprise failures.

Key insights

GenAI's enterprise adoption requires deterministic orchestration, structured interactions, and integration with existing systems, unlike personal productivity tools.

Principles

Method

Break large GenAI tasks into smaller, structured steps returning data classes (e.g., Pydantic models), not just text. Use deterministic orchestration (e.g., GOAP) and integrate with existing domain models and code.

In practice

Topics

Best for: Machine Learning Engineer, CTO, VP of Engineering/Data, Software Engineer, AI Engineer, AI Architect

Related on AIssential

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by GOTO Conferences.