Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
skjhn
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
14 ms
·
31.
▲
by
skjhn
12y ago
Because the data is written to a data structure before the write completed. You can "write" to a cache or to an in-memory database. Databases, relational or NoSQL, write to memory first whether it is to an application managed cach
32.
▲
by
skjhn
12y ago
That's right, and the same is true for MongoDB and Cassandra. They do not fsync on writes and they replicate asynchronously.
33.
▲
by
skjhn
12y ago
Good point. After all, most interactive applications read and write data from local files via SCP and S3.
34.
▲
by
skjhn
12y ago
Do you place a maximum amount of data in that 10s window? If not, it too is arbitrary. I do think batching concurrent writes is nice.
35.
▲
by
skjhn
12y ago
As can Cassandra. It depends on how much data is still in the page cache. I do agree both systems can be configured for immediate durability. However, we went with the default values as most people (and most databases) do not sync on every
36.
▲
by
skjhn
12y ago
Most of the data is read from memory, not all of it. All of it is on disk too.
37.
▲
by
skjhn
12y ago
Performance is a reflection of architecture. Better performance, better architecture. That, and you can never downplay performance.
38.
▲
by
skjhn
12y ago
Well, writes are not durable until fsync. That's true for MongoDB, Cassandra and Couchbase Server. That being said, Cassandra demonstrated great write latency. The issue was read latency.
39.
▲
by
skjhn
12y ago
It can and it is, but it might have to be scaled out. http://www.couchbase.com/liveperson http://www.couchbase.com/paypal
40.
▲
by
skjhn
12y ago
Good catch. Latency is in milliseconds. I'll have to fix that.
41.
▲
MongoDB and DataStax, In the Rearview Mirror
(blog.couchbase.com)
45 points
by
skjhn
12y ago
|
50 comments
42.
▲
DataStax FUD
(blog.couchbase.com)
4 points
by
skjhn
12y ago
|
0 comments
43.
▲
The Real Bitcoin / NoSQL Failure
(blog-shaner.rhcloud.com)
1 points
by
skjhn
12y ago
|
0 comments
44.
▲
MongoDB + Big Data, Almost There
(blog.couchbase.com)
3 points
by
skjhn
12y ago
|
0 comments
45.
▲
Modern Big Data Hadoop
(blog.couchbase.com)
2 points
by
skjhn
13y ago
|
0 comments
46.
▲
MongoDB and Scale Out? No, says MongoHQ
(blog.couchbase.com)
9 points
by
skjhn
13y ago
|
1 comments
47.
▲
The Big Data / Fast Data Gap
(blog.couchbase.com)
1 points
by
skjhn
13y ago
|
0 comments
48.
▲
How important is the architecture / topology of distributed systems?
(blog.couchbase.com)
3 points
by
skjhn
13y ago
|
1 comments
49.
▲
by
skjhn
13y ago
In what ways do you consider them to be different from the point of view of an architect (other than the different clustering implementations)? They're both document databases. They're both distributed. They're both supposed
50.
▲
The Fall of Server Side Web Frameworks
(howtojboss.com)
1 points
by
skjhn
13y ago
|
0 comments