Feels like there's still room for a true capability-driven database SDK—one that standardizes common operations while letting databases expose their strengths through optional capabilities.
Would love to know if anyone is building something along these lines.
#Databases#SDK
Why does every #database require learning a completely different #SDK?
Not because CRUD is different—but because every database exposes its own unique capabilities (#vector#search, change streams, graph queries, #full-text search, etc.).
🧵
We've already seen this pattern work in other ecosystems:
• LangChain → VectorStore interface
• Apache Calcite → Adapter architecture
• Trino → Connector model
• Prisma → Driver adapters
Each abstracts a different layer—but the idea is remarkably similar.
My takeaway:
The future isn't just better prompts.
It's better context.
Choosing what to send may become just as important as choosing which model to use.
Curious—if you were building an AI agent, where do you think most token waste comes from?
Logs? JSON? RAG? Chat history?
One thing people often mix up:
Semantic compression ≠ Prompt caching.
Compression reduces the number of tokens.
Caching avoids recomputing the same prompt prefix.
Different techniques.
Same goal: lower cost and faster inference.