My mental model was completely off coming in. I've been working on retrieval pipelines where "graph" basically means knowledge graph, so I'd expected this to go that direction. The microservices analogy is what clicked it into place for me - it's less about data relationships and more about making the agent's control flow something you can actually inspect and reason about. I'd really want to dig into how ADK handles a fan-out where one node silently fails, since that's been the crack in similar pipelines I've seen.
Head of Backend Engineering at GoodBarber. My team owns the APIs, services and infra that turn no-code projects into real published apps. I write about no-code at scale — and where AI fits in.
Same click here, on several subjects lately. Fifteen years of systems architecture, and I still catch myself arriving, after a day of thinking, at something that was a reflex in microservices four years ago. But what strikes me most is how similar the subjects turn out to be.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
My mental model was completely off coming in. I've been working on retrieval pipelines where "graph" basically means knowledge graph, so I'd expected this to go that direction. The microservices analogy is what clicked it into place for me - it's less about data relationships and more about making the agent's control flow something you can actually inspect and reason about. I'd really want to dig into how ADK handles a fan-out where one node silently fails, since that's been the crack in similar pipelines I've seen.
Same click here, on several subjects lately. Fifteen years of systems architecture, and I still catch myself arriving, after a day of thinking, at something that was a reflex in microservices four years ago. But what strikes me most is how similar the subjects turn out to be.