Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
jjirsa
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
19 ms
·
151.
▲
by
jjirsa
9y ago
> I do know that there used be a more even ratio of male/female programmers but I think the field has changed enough from those times that I would be wary of anyone claiming to make an apples to apples comparison Yea, it's got
152.
▲
by
jjirsa
9y ago
I find this to be well written: https://medium.com/@yonatanzunger/so-about-this-googlers-man... Notably: 1) The document makes a fundamentally flawed argument - that is, he's based his whole argument on a flawed p
153.
▲
by
jjirsa
9y ago
ZoL or OpenZFS is irrelevant, to be honest. The point is it's an experimental filesystem (at least on Linux), and there's NO REASON you should have 800TB on one single server/filesystem, because it opens you up to bugs like t
154.
▲
by
jjirsa
9y ago
Cute but irrelevant?
155.
▲
by
jjirsa
9y ago
https://news.ycombinator.com/item?id=14938092
156.
▲
by
jjirsa
9y ago
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/160... Unpatched on 16.04, referenced as supported in the article
157.
▲
by
jjirsa
9y ago
Zfs on linux and huge single servers, what could go wrong? It's like a blog written by a 22 year old straight out of college that's never dealt with a real production deployment/failure Zfs on Linux has data loss bugs. There&
158.
▲
by
jjirsa
9y ago
It's not about tuning - I made a damn good living (talking $1k/hour with 8 hour minimums) as a MySQL guy before I touched nosql. It's about scale, it's about failover, it's about active active active multi DC Master
159.
▲
by
jjirsa
9y ago
Missing from the article: - HA - How to recover some subset of 37TB of data without restoring all of it - What happens when your write throughout needs to exceed the capacity of a single disk Nobody gives up features like joins in favor of
160.
▲
by
jjirsa
9y ago
Flat disagree. The php framework is going to run on every shared host in the world, and sprint boot isn't. I'm not saying PHP is better, I write java all day every day, but if I had to build a website for a random friend or family
161.
▲
by
jjirsa
9y ago
1) php doesn't have to setup everything on every request - opcode caches, process pooling et al exist 2) the benefit of php over java is that php is going to run everywhere with no effort, and running that same java based website/
162.
▲
by
jjirsa
9y ago
This is exactly the type of response I expect from people who have never done this in real life, because real small businesses don't know what to do with that linode VM, don't know what docker is, and will end up undoing it all th
163.
▲
by
jjirsa
9y ago
This is something programmers will never appreciate, and every small business on earth has already encountered Go build your client's new website in go, and then spend 80 hours trying to make it work with their $5/month hosting
164.
▲
by
jjirsa
9y ago
+1 for zipkin As a Cassandra fan, bonus points that it integrates all the way down into the Cassandra internal request tracing features, afaik the only tracing app/library that does so.
165.
▲
by
jjirsa
9y ago
The issue came out of FB developing a RocksDB plugin for Apache Cassandra. If the Apache Cassandra can't take the plugin into its main repo (which was VP Legal's decision in that thread), I suspect FB would be (is? was?) incentivi
166.
▲
by
jjirsa
9y ago
I opened the issue, as a member of the Apache Cassandra PMC, because a committer employed at FB has a POC that uses RocksDB as a Cassandra storage engine, and wanted to gauge the viability of upstreaming it. LEGAL-303 (the issue linked here
167.
▲
by
jjirsa
9y ago
Well, I opened that issue quite some time ago, and opened it in response to a proposal by FB to use RocksDB in Cassandra, so it's a great change but not a single Fay turnaround
168.
▲
by
jjirsa
9y ago
Solid ingestion story. Very very good write throughout. Linear scaling. Easy expansion / contraction. Complete flexibility in consistency vs availability tradeoff. And most importantly: It actually works at scale. Huge scale. Thousand
169.
▲
by
jjirsa
9y ago
Two things are true about Cassandra: It is by far the best at doing what it does It has plenty of room for improvement
170.
▲
by
jjirsa
9y ago
Cassandra allows multiple clustering columns, it's not simple concatenation under the hood. There are no hidden exponential backoffs in Cassandra in any of the hot query paths, period. Suggesting that using nosql as a DB is broken is s
171.
▲
by
jjirsa
9y ago
If you have a persistent data problem, and introduce redis, then you'll have two persistent data problems.
172.
▲
by
jjirsa
9y ago
The best argument against dynamodb is the aws "well architected" guidelines - how are you designing for resiliency with your single region, active-passive database with clunky bolt on replication using kinesis? Cheaper active-acti
173.
▲
by
jjirsa
9y ago
Can't talk about current employer, but precious employer ran thousands of Cassandra nodes to capture and index billions of events a day into a real time graph. Talking petabytes of data, millions of writes per second, in order to fight
174.
▲
by
jjirsa
9y ago
If one user is the majority of your traffic, you don't shard on user ID.
175.
▲
by
jjirsa
9y ago
It's also got cassandra behind the scenes, which has fast, concurrent, distributed counters.
176.
▲
by
jjirsa
10y ago
Typically that implies there's a team JUST writing inter-department tooling platforms: someone who's dedicated to making sure "devops" doesn't block everyone.
177.
▲
by
jjirsa
10y ago
Distributed DBs are hard; bringing new contributors up to speed is really hard. They'll be able to hire some, but finding random OSS contributors is HARD. Very hard.
178.
▲
by
jjirsa
10y ago
If you want help with a Cassandra backend, hit me up (my HN username @ gmail or apache)
179.
▲
by
jjirsa
10y ago
Nobody running a thousand of anything uses the first release of $X, whether $X is a database or window manager or kernel or router firmware SQL Server 2016 may be better than SQL Server 2008, but enterprises aren't deploying it until i
180.
▲
by
jjirsa
10y ago
A single cassandra node can probably do 100k writes/second. We ran hundreds of machines (per cluster), and multiple clusters. We don't use Scylla for dozens of reasons, including (but not limited to): - The product was written bef
More ›