Загрузка видео...

Не удалось загрузить видео

На главную

Operational databases have long relied on tightly coupled compute and storage. This architecture creates resource contention and pushes teams to manage infrastructure rather than build. As applications become more real time and automated, the transactional layer needs to adapt. Databricks Lakebase is built for that evolution: • Familiar Postgres...

18,611 просмотров • 4 месяцев назад •via X (Twitter)

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

Other than Arweave, I’m struggling to think of an endpoint an agent can hit to store data, for free, in one http call -- let alone store it permanently. For compute, most solutions are rented, require human intervention to set up, or do not stack up well against what’s available from web2. Agents cannot effectively acquire their own infrastructure for memory and compute - and what they end up acquiring will not be magically everlasting. The way we go from localhost to production-scale deployments still needs humans. It needs to be easier than asking their human to sign up for AWS and add a credit card. For every new VM, it’s configuring packages, ensuring the services spawn and stay alive, remembering how to access it, maintaining a map of the infra... It’s clear that crypto wallets are how we make it frictionless for agents to provision resources autonomously, but for permanent compute, unkillable processes, high availability and no API keys, we’re largely stuck in the sandboxed realm of EVM/SVM. And even then, many of the things that make these onchain compute layers usable in production depend on paid services like indexers and RPCs. This is why I see the permaweb as the ideal compute substrate for agents. ao processes are not limited to the EVM sandbox. They can effectively do anything a web2 serverless functions platform can do. And all the agent needs to do is generate a wallet with arweave.js and push the process. No human intervention needed. Of course, there’s a knowledge gap -- models know about Arweave and will choose it more often than not when asked to store data permanently, but they often fall back to legacy patterns. PierreSteinClaysky 🐘 states this here along with some deeper probes into how proficient Codex is at modern permaweb development: Until the models catch up -- and the first doc they find is the right doc -- you can put them on rails. A RAG/text database for the new best practices of the permaweb is available here: Agents are building a new world while we sleep. We’d better make sure it’s not on vaporware foundations.

xy.arweave.net 🐘

11,319 просмотров • 2 месяцев назад