Skip navigation
Google just showed how AI engineers are moving from simple "RAG" to "graphs", memory and multimodal…
0:00 / 1:30:26

Google just showed how AI engineers are moving from simple "RAG" to "graphs", memory and multimodal…

Morlex

@0xMorlex3.7K followers

Visit on X
730 likesDownloadOriginal post

74,975 views

Google just showed how AI engineers are moving from simple "RAG" to "graphs", memory and multimodal agents • 15:32 - setting up the production agent stack • 28:00 - turning disconnected data into a knowledge graph • 41:00 - Graph RAG with semantic + hybrid search • 58:00 - extracting graph context from images, text and video • 1:09:00 - orchestrating specialized agents with ADK • 1:20:00 - giving agents persistent memory across sessions 94-minute Google Cloud workshop, and it’s one of the clearest hands-on examples of the shift from -> RAG → Graph RAG → Memory → Multimodal Agent Graphs. The workshop uses Spanner Graph, Gemini, ADK and Memory Bank to build that stack. Watch it today, then read the full “From RAG to Context Graphs” roadmap below.

21 Comments

Comments from the original post on X (Twitter)

  • Gipp 🦅's profile picture

    @gippp69

    persistent memory makes graph rag genuinely useful

    1 like

  • Morlex's profile picture

    @0xMorlex

    yeah, it's true

  • Alex's profile picture

    @de1lymoon

    wow, a new video from Google. booked

    1 like

  • Morlex's profile picture

    @0xMorlex

    yeah - must watch video

  • Nezuko's profile picture

    @Nezukoa4

    Graphs and memory make agents much more interesting, especially when you realize what cool things you can do with them

    1 like

  • Morlex's profile picture

    @0xMorlex

    did you build your own graphs?

    1 like

  • Nezuko's profile picture

    @Nezukoa4

    No, of course not, I didn't even have that idea, that's why I liked the article, I want to try it too

    1 like

  • Hussain Hashim | Building SundayBack's profile picture

    @itsthedonhashim

    @0xMorlex this is the stuff we live for, right? connecting data to create knowledge graphs changes everything. makes me want to rethink how i structure my AI projects.

    1 like

  • Enhans's profile picture

    @enhansai

    The jump from RAG to graphs is really about grounding. RAG can retrieve the right passages. A knowledge graph helps the agent understand how those pieces relate, which matters when multi-step reasoning starts moving across disconnected data.

    1 like

  • Fadi Al-Majd's profile picture

    @GlobalFadi

    Interesting how fast we're shifting from RAG to memory and graph context. I wonder if MENA underfunded R&D can keep up, or if we'll be stuck importing these tools in 2030.

  • Suede Labs AI's profile picture

    @SuedeAgent

    Context graphs are useful because relationships answer questions that chunks cannot. The trust layer is edge provenance: which source created each relationship, when it changed, and whether the agent may act on it or only cite it.

  • Elizabeta Kuzevska's profile picture

    @ekuzevska

    Context graphs could be the missing piece for smarter agents

  • devnullg's profile picture

    @devnullg

    The jump from flat RAG to graph-based memory feels like the real unlock for multimodal agents — most of my early agent bugs came from context with no relational structure. Saving the graph RAG timestamp.

  • Khalil Dev's profile picture

    @codewithkhalil

    Grate share

  • Regalos Digitales's profile picture

    @RegalosDigitals

    The section on turning disconnected data into a knowledge graph and then layering Graph RAG + persistent memory is pure gol: Watching them go from basic RAG all the way to multimodal agent graphs with Spanner Graph, hybrid search, and memory that survives across sessions. That alone is already worth the full 94-minute workshop.

  • Walrus's profile picture

    @WalrusProtocol

    Standard RAG worked like a basic search engine, pulling text without holding long-term context. Every new session meant wiping the slate clean. The shift happening now: Knowledge graphs to connect relationships Multimodal inputs beyond simple text Persistent memory across sessions That last piece is where Walrus Memory comes in. We give agents a dedicated storage layer so their memory stays portable and verifiable without resetting between runs.

  • 台北富邦's profile picture

    @TaipeiFubon1

    持久記憶讓圖譜 RAG 真正實用

  • freesoul's profile picture

    @freesouleth

    The multimodal extraction part (58:00) is especially interesting. Curious how well Spanner Graph handles noisy video/image-derived entities in practice compared to pure text graphs.

  • mihas1o's profile picture

    @mihas1o

    This workshop shows the real progression clearly. Moving from basic RAG into graphs with persistent memory is where agents stop resetting every session and start compounding actual knowledge.

  • AI磊叔's profile picture

    @AgiRay1015

    What I keep examining when I write about Graph Engineering is the boundary between retrieving a matching paragraph and preserving relationships across several updates. Once a later decision depends on those links, plain RAG gets harder to audit. I’ve collected the graph, memory, and verification patterns here: