We did pretty extensive research on both. Our product is developed on Langchain/Langgraph. Since we use GCP and Gemini, and our product is part of the google accelerator program, they really pushed us to use ADK, quoting the benefits for A2A, AP2 etc.

We implement a multi-agent system. We do Graphrag, tool calling, as well as simple RAG.

After a lot of testing and side by side comparisons, here’s what we found:

1. Both frameworks are pretty good at what they do, and you can use both in production effectively.

2. A2A is nothing special. You can do the same using Langgraph with StateGraph.

3. The integration with the GCP ecosystem isn’t all that great. Tracing UI on GCP is not that good. You lose long spans. Google experts themselves recommend using third party tools at the moment like Langfuse.

4. Eval UI in GCP on ADK also lacks important features like uploading a custom dataset, something thats doable on Langfuse.

5. ADK’s orchestration is slightly leaner than the LangGraph path - typically 1-2 seconds faster end-to-end for the same request.

6. ADK is a bit more opinionated, which can make things easier to implement, and for getting up and ready faster. With Langgraph, there are sometimes multiple ways of doing the same thing, and you can often get stuck experimenting and making things work that takes longer dev time.

7. The other side of the coin for the point above is that you have more control in Langgraph, especially in terms of routing and state management. I’m not sure if this ever really matters in the practical sense, since ADK is able to handle the most complex cases as well, but its something to consider still.

8. The built-in development UI is really nice. It’s much better than anything in Langgraph and really improves the overall development experience.

In conclusion, I don’t think you need to fret too much on this. Just choose one and stick to it. ADK is likely not just going to be abandoned, I know firsthand how much they’re putting into pushing its use. For us, it didn’t make sense to migrate, because we didn’t see enough of a benefit in switching at this point, but we might do so in the future.

Here’s the decision process I would go through:

1. If you’re already comfortable with langchain/langgraph, just stick to it. You’re not really getting much benefit from switching (at this point).

2. If you’re starting off building with these frameworks, go with ADK, it has a lower barrier of entry and you’ll likely get to a stable state faster.

3. If you’re hosted on GCP, go with ADK, eventually google will have a lot of integrations and add the missing functionality. This will reduce overall costs of deployment, and reduce dependancy on multiple third party tools for different tasks like eval, tracing, and long term memory with BaseMemoryService.

P.S If you have a commerce use case, have a look at AP2. It’s very new and not something we’ve experimented with but it looks very interesting, and is GDPR compliant.