Update _posts/2025-05-08-agentic-ai-with-quarkus-p3.adoc

Co-authored-by: Clement Escoffier <[email protected]>

Author: mariofusco

_posts/2025-05-08-agentic-ai-with-quarkus-p3.adoc

@@ -102,7 +102,7 @@ public String requestAgentic(String request) {
 
 == Comparing the workflow and agentic approaches
 
-The two approaches are equivalent in terms of functionality, but they differ in the way they are implemented and the levels of control and flexibility that they offer. In particular the pure agentic solution is much simpler and more elegant, as it does not require any additional code to route the request to the right expert. The agent is able to do that by itself. It could also decide to use more than one expert if needed, something that would be impossible to do with the workflow approach, where the routing is hardcoded in the application code.
+The two approaches are equivalent in terms of functionality, but they differ in how they are implemented and the levels of control and flexibility they offer. In particular, the pure agentic solution is much simpler and more elegant, as it does not require additional code to route the request to the right expert. The agent can do that by itself. It could also use more than one expert for a single query if needed, which would be impossible with the workflow approach, where the routing is hardcoded in the application code.
 
 On the other hand, the workflow approach is more predictable and easier to debug, as the routing logic is explicit and can be easily traced. For instance, the behavior of the Router Agent alone  could be controlled and corrected with an output guardrail. Moreover, it also allows for more complex workflows, where the routing decision can depend on multiple factors and not just on the user request.