Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
skyde
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
12 ms
·
91.
▲
by
skyde
4y ago
what do you call "neat hacks instead of actual math "? kahn Academy is teaching the Common Core math, and I don't see how it's not actual math.
92.
▲
by
skyde
4y ago
("Occupations" -> "Writers") seem wrong why would you do this? same for ("Categories with more than 100 entries" -> "Writers"). This seems like trying to put tag on category entity instead of
93.
▲
by
skyde
4y ago
Right with real transaction you could maintain your own index if you really need them. And to have good performance you should never join entity that have distinct partition key. Otherwise you end up reading too much data over the network.
94.
▲
by
skyde
4y ago
microsoft already have Managed citusDB. it’s called Azure postgresql Hyperscale! They probably just renamed it and are making a big deal about it but in the end will confuse all customers as to why it’s unrelated to cosmosdb and to cosmos d
95.
▲
by
skyde
4y ago
this is a game changer !
96.
▲
by
skyde
4y ago
Systems Performance: Enterprise and the Cloud 1st Edition Edition ISBN-13: 978-0133390094, ISBN-10: 9780133390094
97.
▲
by
skyde
4y ago
The Rust Programming Language ISBN-13: 9781718500440
98.
▲
by
skyde
4y ago
this is my understanding as well! but i might be wrong. Asp.net webform where not really interactive. Any change to the UI require reloading the page.
99.
▲
by
skyde
4y ago
This is definitely about tradeoffs. But there is 2 tradeoffs spectrum, 1- Consistent (strict serializability + global transaction) vs Eventual consistency. 2- Range query and Join vs KeyValue only FoundationDB provide a Consistent databs
100.
▲
by
skyde
4y ago
You are correct that if you have a singleton server returning monotonic time to clients this would work. But this Monotonic time server is not part of Cassandra itself and for this reason majority of the people using Cassandra will use the
101.
▲
by
skyde
4y ago
Since "client B write" was successfully written on 2 of the 3 nodes. Any read request that read only from 2 of the 3 nodes instead of using quorum read, will be able to see what Client B wrote until it magically disappears. Quorum
102.
▲
by
skyde
4y ago
This new « accord » thing look very promising! If this get merged into Cassandra this change everything! A prototype has been developed that has demonstrated its correctness against Jepsen.io’s Maelstrom tool
103.
▲
by
skyde
4y ago
Client À write value 1 on 2 of 3 node with timestamp=3 then later client B write value 2 on 2 of the 3 node with timestamp=1 then read repair happen and (value=1 timestamp=3) is written to all 3 nodes. this is only one of many scenarios wh
104.
▲
by
skyde
4y ago
timestamp is coming from the operating system where the client library is running. so unless all your write request are issued by the same machine then you are guaranteed to face the problem where the client machine clocks are not in sync.
105.
▲
by
skyde
4y ago
LWT is still the only way to guarantee your write don’t random disappear and that conditional update are really conditional. LWT still have awful performance compared to a write request with same guarantee in any other database.
106.
▲
by
skyde
4y ago
why settle for noSQL when we can use newSQL? Cockroachdb, CitusDB, TiDB,Yugabyte …
107.
▲
by
skyde
4y ago
please tell me more about General purpose transaction! I really hope they work Kyle Kingsbury.
108.
▲
by
skyde
4y ago
sorry to disappoint you but there is a reason Cassandra tried to add LWT using paxos. it mostly work but it’s extremely slow and still have many bugs. https://www.datastax.com/blog/lightweight-transactions-cassa...
109.
▲
by
skyde
4y ago
eventually they will converge on a « random » value! that’s why we say it’s write quorum is not consensus it’s offer very weak guarantee
110.
▲
by
skyde
4y ago
it’s worse than waiting actually. Because client A might write value « 1 » and after client B write value « 2 ». Then client C can read Value 2 for 5 minute and then cassandra internal read-repair eventually put value 1 on all replica and
111.
▲
by
skyde
4y ago
thanks a lot. I didn’t realize that because TTL was present this could be optimized.
112.
▲
by
skyde
4y ago
I have a question for someone with your expertise. Why not use the CLOCK-Pro cache eviction algorithm in a system like this?
113.
▲
by
skyde
4y ago
driving a prius ?
114.
▲
by
skyde
4y ago
yes it’s more modular with clear contract between the parts
115.
▲
by
skyde
4y ago
this is risky move. lot of artist already moved to Vimeo because of quality in the past.
116.
▲
by
skyde
4y ago
even in the case of soft-realtime we don't say the system is real-time because it's fast. We say its realtime because majority of the time it meet its deadline.
117.
▲
by
skyde
4y ago
Real-time software does not mean fast software! It mean determinism, guarantee that each time it run it will never take more than x milliseconds to complete. Those guarantee are very hard when considering a system like linux with many backg
118.
▲
by
skyde
4y ago
you hear people from minority group all the time saying they want to keep the bloodline pure and not dare someone from a different races. If a white people said this everyone would say he is a nazi.
119.
▲
by
skyde
4y ago
if you care more about what happened hundreds of years ago (racism against group A) than what is happening now (racism against group B). you are part of the problem!
120.
▲
by
skyde
4y ago
again quic is not just Http. you can proxy an sftp connexion through quic. By having a (tcp to quic) gateway at the source and a (quic to tcp) relay at the destination. I have seen this implemented in production!
More ›