Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
bluecmd
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
91.
▲
by
bluecmd
11y ago
The best course of action is to not store the data at all. Use "Sign in with Facebook" et. al and never even get the user password for example. I'm so tired of needing to have a password manager when we have good authenticati
92.
▲
by
bluecmd
11y ago
Ah OK. This might sound harsh, but so the guarantee you have is that the data will not be lost? That's a pretty weak guarantee no? Also, best effort implies no ordering in the worst case no? I always try to judge systems when the world
93.
▲
by
bluecmd
11y ago
I find it interesting that the article claims eventual consistency, but also best effort ordering. The consistency in a queue is surely made of two parts: count and order. To not have duplicates is nice, but if ordering is not guaranteed -
94.
▲
by
bluecmd
11y ago
Aha! Re-reading your previous comment I understood what you meant. So Cassandra has a "logical" key that is the primary key, and the actual key from HBase-like DBs is derrived from cluster key and the primary key. So in essence it
95.
▲
by
bluecmd
11y ago
I know all that, I have extensive experience with NoSQL databases like HBase. But the thing I'm asking about how does Cassandra handle CPU hotspotting on a single row. If you have timestamp as a column you will never be able to shard a
96.
▲
by
bluecmd
11y ago
Hm. How does Cassandra really handle rows if the author is recommending storing timestamps in the same row? Sounds like a really good way of getting un-shardable atoms (whatever that's called in Cassandra) and hotspots.
97.
▲
by
bluecmd
11y ago
Heard of encryption?
98.
▲
by
bluecmd
12y ago
Yes, as long as both endpoints (TCP/IP stacks) keep their state it doesn't matter what stuff does between them. Interfaces being one of the things being between stacks. That is what allows for stuff like live application migration
99.
▲
by
bluecmd
12y ago
Devil is in the details, but the source actually talks against you here: This happens because your router or firewall is trying to clean up dead connections. It's seeing that no data has been transmitted in N seconds and falsely a
100.
▲
by
bluecmd
12y ago
I'm pretty sure you're wrong. Mind citing a source on that the connection should terminate? I'm fairly certain that the connection stays alive and that SSHd doesn't need to care about this, all handled on OS-level. That&
101.
▲
by
bluecmd
12y ago
While layouting an full-custom SPI bus for an IC I had to do the same thing. It simply made sense to sacrifice programming model in that case to layout simplicity.