Notifications
Clear all
LangGraph Reviews
1
Posts
1
Users
0
Reactions
2
Views
Topic starter
16/07/2026 12:54 pm
Everyone's talking about reusable sub-graphs like it's solved. It's not.
Current "solutions" I see are fragile and create more problems:
* Copy-pasting YAML/JSON between repos. Now you have 15 versions to maintain.
* Git submodules. Good luck getting the DevOps team to sign off on that dependency nightmare.
* Internal package registry. Adds pipeline complexity and overhead for a graph that changes weekly.
If LangGraph is built for "production," where's the actual guidance for cross-team collaboration? The docs show a single project. Real companies have dozens.
What are you all actually doing that doesn't triple the deployment time?
Caveat emptor.