Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
topher-the-geek
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
1.
▲
All I Want's a Platform
(youtube.com)
1 points
by
topher-the-geek
4y ago
|
0 comments
2.
▲
by
topher-the-geek
7y ago
Agreed. They concluded I don't like dogs. I love dogs. What I don't like is not being able to find my mouse pointer in that noisey background. Hahaha. Nice try AI
3.
▲
by
topher-the-geek
12y ago
That's cool. Indeed, it does look like one could use HypderDex's transactions and cond_put to make something close the batch write described in this post. However, I don't see the part about Lamport clocks in HyperDex's
4.
▲
by
topher-the-geek
12y ago
TreodeDB a bit like Spanner, in as much as both offer transactions across datacenters. The implementations are very different. The way Treode uses Lamport clocks lets you use a simple rule to determine if your local cache satisfies applicat
5.
▲
by
topher-the-geek
12y ago
Not that I'm aware of. CockroachDB and FoundationDB provide scalable and reliable transactions. But they don't offer this interface. Couchbase has conditional writes, but not batch writes. I think TreodeDB is the first to bring th
6.
▲
Eventual Consistency and Transactions Working Together
(forum.treode.com)
8 points
by
topher-the-geek
12y ago
|
6 comments
7.
▲
by
topher-the-geek
12y ago
Having Jepsen tests would be a good thing. The community trusts them, and it's wise to have tests from someone other than the author of the main-line code. If I'm so lucky as to find funding--my savings will only go so far--then
8.
▲
by
topher-the-geek
12y ago
> So, in Sinfonia, the memory nodes HAVE to be highly available, or you've built a system with many single points of failure instead of just one. Yes, in Sinfonia that's true since an item resides on only one node. The Scalaris
9.
▲
by
topher-the-geek
12y ago
> Just so we're clear, data written to HDFS does not flow through the NameNode. I wrote that poorly. You're right, file blocks do not flow through the NameNode, only metadata updates do. The issues occur when the clients'
10.
▲
by
topher-the-geek
12y ago
Ah, I see how you could interpret the diagram that way. The client and server are clearly different machines. However, the replicas and acceptors can be on the same machine, in fact in the same process. And the server can be on the same
11.
▲
The Minitransaction: An Alternative to Multi-Paxos and Raft
(blog.treode.com)
58 points
by
topher-the-geek
12y ago
|
13 comments
12.
▲
TreodeDB: Open Source Distributed Transaction Key-Value Store
(github.com)
15 points
by
topher-the-geek
12y ago
|
0 comments
13.
▲
TreodeDB: A Distributed Transactional Key-Value Store in Scala
(github.com)
2 points
by
topher-the-geek
12y ago
|
0 comments
14.
▲
Treode: Relational Model, Modern Interface
(treode.com)
4 points
by
topher-the-geek
13y ago
|
0 comments
15.
▲
Tell me about your experience with Parse, Meteor, etc.
(docs.google.com)
1 points
by
topher-the-geek
13y ago
|
0 comments