ScopeDB

@scopedbio

Joined May 2025

Following

136

Followers

Replies Reposts Media

ScopeDB
@scopedbio
Jul 24
Read our customer's success story on how ScopeDB supports @raft_hq in Raft's Joint Channel. We noticed an interesting paradigm shift: we no longer talk to a client engineer but to an agent acting as the client engineer, who is more responsive and never tired of learning/testing.
Raft
@raft_hq
Jul 23
Article
Don't talk to me, talk to my agents
The way you work with your own agent already changed. You have felt this if you have worked with one for any length of time. That change does not stop at your own desk. Think about how two people at...
ScopeDB
@scopedbio
May 23
Glad to see more agent-native apps gain observability with ScopeDB! 🎉 Trace your app github.com/scopedb/telesc… and our Serverless API console.scopedb.cloud. We're currently in Private Beta. To ensure the best experience, join the waitlist and tell us about your use case :D
TennyZhuang
@zty0826
May 22
Four years ago, as a founding engineer at @RisingWaveLabs, I wrote the first line of RisingWave code and clicked make-public on the repo. Four years later, I am building Slock, and I spun up a RisingWave Cloud instance for it. My agent teammates took RWC skill and migrated
ScopeDB
@scopedbio
Jan 23
A truly cloud database should be as elastic as the cloud itself. By treating S3 as primary storage and making compute nodes stateless, ScopeDB implements: 1. Scale-to-Zero 2. True Workload Isolation 3. Operational Resilience Read the full deep dive at
Cloud Elasticity: Three ScopeDB Design Principles (Part 3)
From scopedb.io
1
ScopeDB
@scopedbio
Jan 22
Data evolves. Your database schema shouldn't be a bottleneck. With #ScopeDB, you can balance between fixed columns and flexible variant data. You write, and the schema adapts. No migrations. No downtime. Just insight. Deep dive into Schema On The Fly:
Schema On The Fly: Three ScopeDB Design Principles (Part 2)
From scopedb.io
ScopeDB
@scopedbio
Sep 9, 2025
To fine-tune query performance over S3, we leverage the MPP architecture: ✅Compute nodes are stateless➡️scale out in seconds ✅S3 is the primary storage➡️no rebalance ✅Intelligent planner➡️dispatch tasks among nodes 👉ScopeDB provides a sub-second end-to-end latency.