codefarm
HomeRoadmapsGuidesQuizzesMentorshipWhiteboardEbooksCodeSmash
Learn
RoadmapsQuizzesBlogsVideosGuides
Simulators
Why API GatewayWhy Load BalancerWhy Circuit BreakerKafka Message FlowKafka Consumer LagKafka RebalanceRate LimitersUptime SLALatency SimulatorCachingConsistent Hashing
Tools
UUID GeneratorDate & Time ToolsJWT DecoderText FormatterMind MapFun PuzzlesKids Learning
Profile
Back to Spring AI
🧭
Phase 5

Embabel: Goal-Oriented Agent Orchestration

When hand-rolled ReAct and Plan-and-Execute loops stop scaling, reach for a real planner. GOAP, the Blackboard, and building agents with @Agent, @Action, and @AchievesGoal.

1

GOAP: Why Embabel Plans Instead of Prompts

Why the fintech team's hand-rolled Plan-and-Execute refund flow turned into an unmaintainable if/else tree, and how Goal-Oriented Action Planning replaces hand-written branching with a real planner.

spring-aiembabelgoap
2

Building Agents: @Agent, @Action & @AchievesGoal

A real Embabel agent, built from the framework's own official bank-support example and adapted to Acme Fintech: @Agent, @Action, the Blackboard in practice, unit testing, and running it from a shell and a REST controller.

spring-aiembabelagent
3

When to Reach for Embabel vs Plain Spring AI

The same refund-adjudication problem, solved three ways — a plain @Tool loop, a hand-rolled Plan-and-Execute pattern, and an Embabel agent — with a concrete decision framework for picking between them.

spring-aiembabeldecision-framework
codefarm

Learn backend engineering with clear roadmaps, practical tools, and interactive quizzes. From zero to production-ready.

Learn

  • Roadmaps
  • Guides
  • Blogs
  • Videos
  • Ebooks

Labs

  • Simulators
  • Quizzes
  • Whiteboard
  • JWT Decoder
  • UUID Generator
  • Toolbox

Simulators

  • Uptime SLA
  • Rate Limiters
  • Kafka Message Flow
  • Kafka Consumer Lag
  • Kafka Rebalance

Community

  • Cohorts
  • Testimonials
  • About
  • Contact

Legal

  • Terms & Conditions
  • Privacy Policy
  • Refund & Cancellation