The Embabel Agent Framework, launched by Spring founder Rod Johnson, is a new JVM-based platform for building AI-powered applications built on the Spring Framework. It aims to transform how developers integrate large language models (LLMs) with conventional Java applications, shifting from experimental approaches to production-ready, type-safe solutions.
Embabel models “agentic flows” using actions, goals, and conditions. Unlike simpler frameworks, it leverages Goal-Oriented Action Planning (GOAP), an AI algorithm traditionally used in gaming, for proper planning. This allows applications to perform tasks that weren’t explicitly programmed to do by combining steps in novel ways and dynamically replanning after each action, forming an OODA loop.
A core tenet of Embabel is its strong typing and object orientation. This ensures all LLM interactions are strongly typed, offering compile-time checking, refactoring support, and IDE assistance, aligning AI development with disciplined engineering practices.
Rod Johnson highlighted that Embabel treats planning as a distinct capability, leveraging specialized algorithms rather than relying solely on LLMs. The framework’s GOAP implementation determines optimal action sequences by considering preconditions and effects. This yields several benefits: enhanced efficiency by minimizing unnecessary LLM calls, dynamic adaptability through replanning, increased composability by allowing new actions and goals without modifying existing code, and the ability to parallelize actions. This planning cycle significantly improves reliability for complex, multi-step processes.
The framework supports three execution modes: Focused (specific agent calls), Closed (user intent classifies agent selection), and Open (the platform assesses user intent to achieve goals using all available resources). Embabel also prioritizes ease of testing, with agents being unit testable like Spring beans and a dedicated library for prompt testing. Its extensibility allows adding domain objects, actions, goals, and conditions without altering existing code.
The framework also provides a clear separation between the programming model and platform internals, enabling local runs and higher quality of service in production. It supports LLM mixing for cost-effectiveness and enhanced capability, including local models for privacy and cost management.
Embabel brings agent capabilities to the JVM ecosystem, building on Spring AI with higher-level abstractions for complex requirements. It addresses key AI application development challenges by maximizing reuse, facilitating testing, increasing composability, enhancing manageability, and providing type safety.
InfoQ engaged with Rod Johnson, the founder of Embabel and Spring, to gain further insights into the framework’s design and strategic positioning.
InfoQ. Why Kotlin for Embabel, given the advancements in modern Java?
Rod Johnson: Java has done remarkably well under Oracle’s stewardship. Modern Java is certainly much improved. I personally prefer coding in Kotlin and feel that using Kotlin accelerates Embabel’s development. I particularly like null safety, more readable collection usage with no need to lift to streams, and more concise syntax. Reification also makes pure Kotlin usage more elegant by reducing the impact of type erasure.
However, the choice of language for implementing the framework does not imply anything about the choice of language to build applications on it. I would encourage all JVM developers to consider Kotlin, but there are good reasons why many projects remain in Java. Kotlin has outstanding interop with Java. It’s painless. We’re committed to ensuring that Java usage is entirely idiomatic, without any Kotlin influence. Where necessary, we add a little Java code to ensure that. For example, you’ll never see a Kt import if you build applications in Java.
Embabel’s core values of type safety and a rich domain model stand out whether you build in Kotlin or Java. We aim to be idiomatic in both languages–there’s also a Kotlin DSL.
Embabel is a JVM framework, not a Kotlin framework. We know that the dominant language on the JVM is Java, and it’s great that Java is moving forward.
InfoQ: How do you position Embabel relative to other Java-based AI initiatives like LangChain4j and Spring AI?
Rod Johnson: Embabel is a much higher level than LangChain4j and Spring AI. It builds on that layer, choosing Spring AI due to its affinity with the Spring ecosystem, but it offers a higher level of abstraction and introduces original ideas. The agent framework level is already familiar in Python, but it’s very new on the JVM. And it’s urgently needed if Java is going to maintain its position in the enterprise and beyond.
InfoQ: Can traditional Java teams adopt Embabel, or is AI expertise required?
Johnson: I think that understanding of the domain and existing business applications and infrastructures is vital to making Gen AI deliver business value. Embabel aims to make it as easy for JVM developers to write agents as to write Spring MVC applications, using their core skills.
Many people and organizations think that you need to write Gen AI applications in Python. That means a new stack to put into production, potentially a new skill set and a lot of friction in getting at existing business logic and infrastructure. I believe that that is entirely wrong–and I’m very familiar with the Python ecosystem. Java teams are well-positioned to leverage AI in their applications, with minimal friction and the benefit of their existing understanding and toolset.
Having said that, LLMs are a powerful new technology with far-reaching implications. Organizations and developers need to understand the risks and costs as well as the rewards. A good agent framework will make Gen AI safer and more predictable, but it’s still essential to understand the forces at work. And that caveat applies to whatever tech stack you build your applications on.
InfoQ. Given your history with Spring and current relationship with the ecosystem, how do you see Embabel’s evolution in relation to Spring AI and the broader Spring portfolio? Are there discussions about closer integration or potential inclusion in the official Spring family of projects?
Johnson: I just spoke at Spring I/O in Barcelona. It was a great show. I’m very happy to build on Spring, because Spring is a great technology, and as it’s the dominant component model in enterprise Java, it’s a no-brainer from an adoption standpoint. Of course, I’m also happy to build on Spring for personal reasons. It’s a joy to see something I gave birth to 23 years ago thriving and in good hands.
Embabel is an independent project with novel ideas and the goal of being the best agent framework on any platform. It’s a much higher level than Spring AI and introduces novel ideas. I think its existence is a good thing for Spring and Java.
When I created Spring, I was focused on solving the most important enterprise Java problem at that time–the fact that J2EE made it way too hard to build applications. In creating Embabel, I’m focused on solving the most important JVM problem of today: how to bring business applications into the Gen AI era.
While I think the JVM has a particularly important role to play in the future of Gen AI, Embabel’s goal of being the best agent framework anywhere means eventually porting the model to other platforms, something that doesn’t apply to Spring. I can definitely see a TypeScript version (I won’t say port as it would need to be idiomatic), as I like TypeScript, and Node is important. And obviously, Python is very popular.
I believe Embabel can be as important a technology as Spring, while expanding the power of the Spring ecosystem.
InfoQ: Where can developers find examples and learning resources for Embabel?
Johnson: We’re continually working to improve the examples. The embabel repository is the starting point for exploration and contains instructions for getting started. There are example agents under the embabel-agent-examples
subdirectory of that repository. The coding agent doubles as an example and is in its own repository at https://github.com/embabel/ embabel-coding-agent.
We plan to evolve examples like the coding agent and travel planner to the point where they’re not only helpful for developers learning Embabel but genuinely useful. I can definitely see some of them becoming interesting open-source projects in their own right.
