We're handing out report cards on big offseason moves, including Monday's trade for offensive tackle Tytus Howard.
from www.espn.com - TOP https://ift.tt/QM6IonO
Senin, 02 Maret 2026
Minggu, 01 Maret 2026
Inside the secret history of the black mamba
In late 2002, Nike began creating a global campaign featuring the black mamba -- and presented it to an NBA superstar. That star was not Kobe Bryant.
from www.espn.com - TOP https://ift.tt/bPOYQ05
from www.espn.com - TOP https://ift.tt/bPOYQ05
Draft guide: Rankings, tips, strategy, stats and more
All the rankings, projections, cheat sheets, strategy and analysis you need for the 2026 fantasy baseball season.
from www.espn.com - TOP https://ift.tt/g7JVWfq
from www.espn.com - TOP https://ift.tt/g7JVWfq
Sabtu, 28 Februari 2026
Betting buzz: Kon Knueppel overtakes Cooper Flagg as NBA Rookie of the Year favorite
Kon Knueppel's hot play has shaken up the Rookie of the Year odds, as the Hornets' star passes Cooper Flagg as the favorite.
from www.espn.com - TOP https://ift.tt/LOAw046
from www.espn.com - TOP https://ift.tt/LOAw046
New top story on Hacker News: Show HN: SQLite for Rivet Actors – one database per agent, tenant, or document
Show HN: SQLite for Rivet Actors – one database per agent, tenant, or document
13 by NathanFlurry | 2 comments on Hacker News.
Hey HN! We posted Rivet Actors here previously [1] as an open-source alternative to Cloudflare Durable Objects. Today we've released SQLite storage for actors (Apache 2.0). Every actor gets its own SQLite database. This means you can have millions of independent databases: one for each agent, tenant, user, or document. Useful for: - AI agents: per-agent DB for message history, state, embeddings - Multi-tenant SaaS: real per-tenant isolation, no RLS hacks - Collaborative documents: each document gets its own database with built-in multiplayer - Per-user databases: isolated, scales horizontally, runs at the edge The idea of splitting data per entity isn't new: Cassandra and DynamoDB use partition keys to scale horizontally, but you're stuck with rigid schemas ("single-table design" [3]), limited queries, and painful migrations. SQLite per entity gives you the same scalability without those tradeoffs [2]. How this compares: - Cloudflare Durable Objects & Agents: most similar to Rivet Actors with colocated SQLite and compute, but closed-source and vendor-locked - Turso Cloud: Great platform, but closed-source + diff use case. Clients query over the network, so reads are slow or stale. Rivet's single-writer actor model keeps reads local and fresh. - D1, Turso (the DB), Litestream, rqlite, LiteFS: great tools for running a single SQLite database with replication. Rivet is for running lots of isolated databases. Under the hood, SQLite runs in-process with each actor. A custom VFS persists writes to HA storage (FoundationDB or Postgres). Rivet Actors also provide realtime (WebSockets), React integration (useActor), horizontal scalability, and actors that sleep when idle. GitHub: https://ift.tt/zLHmSjJ Docs: https://ift.tt/5ThN1yM [1] https://ift.tt/G8LRU3E [2] https://ift.tt/0JlZ5vG... [3] https://ift.tt/LaJmBns
13 by NathanFlurry | 2 comments on Hacker News.
Hey HN! We posted Rivet Actors here previously [1] as an open-source alternative to Cloudflare Durable Objects. Today we've released SQLite storage for actors (Apache 2.0). Every actor gets its own SQLite database. This means you can have millions of independent databases: one for each agent, tenant, user, or document. Useful for: - AI agents: per-agent DB for message history, state, embeddings - Multi-tenant SaaS: real per-tenant isolation, no RLS hacks - Collaborative documents: each document gets its own database with built-in multiplayer - Per-user databases: isolated, scales horizontally, runs at the edge The idea of splitting data per entity isn't new: Cassandra and DynamoDB use partition keys to scale horizontally, but you're stuck with rigid schemas ("single-table design" [3]), limited queries, and painful migrations. SQLite per entity gives you the same scalability without those tradeoffs [2]. How this compares: - Cloudflare Durable Objects & Agents: most similar to Rivet Actors with colocated SQLite and compute, but closed-source and vendor-locked - Turso Cloud: Great platform, but closed-source + diff use case. Clients query over the network, so reads are slow or stale. Rivet's single-writer actor model keeps reads local and fresh. - D1, Turso (the DB), Litestream, rqlite, LiteFS: great tools for running a single SQLite database with replication. Rivet is for running lots of isolated databases. Under the hood, SQLite runs in-process with each actor. A custom VFS persists writes to HA storage (FoundationDB or Postgres). Rivet Actors also provide realtime (WebSockets), React integration (useActor), horizontal scalability, and actors that sleep when idle. GitHub: https://ift.tt/zLHmSjJ Docs: https://ift.tt/5ThN1yM [1] https://ift.tt/G8LRU3E [2] https://ift.tt/0JlZ5vG... [3] https://ift.tt/LaJmBns
Jumat, 27 Februari 2026
Langganan:
Komentar (Atom)