Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
thermodynthrway
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
11 ms
·
61.
▲
by
thermodynthrway
8y ago
This is just not true. Google uses almost entirely immediately consistent databases and gRPC internally. Eventual consistency is hardly ever required for REST type calls even at massive scale. gRPC has no queuing and the connection is hel
62.
▲
by
thermodynthrway
8y ago
I've heard of even Unicorns throwing consistency out the window. Apparently Netflix has a bunch of "cleanup jobs" that comb the database for various inconsistencies that inevitably show up. You can't have consistent micr
63.
▲
by
thermodynthrway
8y ago
A thousand small balls of mud that communicate with each other randomly is nearly impossible to grok because the IDE can't save you
64.
▲
by
thermodynthrway
8y ago
Nah, just use a database that can scale with your app and run a ton of instances. You'll be hard pressed to find any size app that doesn't fit in RAM these days.
65.
▲
by
thermodynthrway
8y ago
I've worked on a system that used Kafka in-between. It makes consistency issues a ton worse because everything is async. At least with HTTP you can do synchronous calls
66.
▲
by
thermodynthrway
8y ago
I've seen it on monoliths too. We run a pretty large app just fine with the "nuclear option". Database transaction isolation level serial. Makes it impossible to have inconsistencies on the database level, and on some RDBMS l
67.
▲
by
thermodynthrway
8y ago
With web apps the main concern is data consistency between relations. On the OS level you have these same concerns with memory and disk, and there's database-like systems in the kernel and drivers to handle it. Essentially all these ut
68.
▲
by
thermodynthrway
8y ago
I've always said if the Linux kernel can be a giant monolith, in C no less, than there's maybe 100 web applications in the world that need to be split into multiple services. I've worked with microservices a lot. It's a
69.
▲
by
thermodynthrway
8y ago
There's a limited supply of people with the education and life opportunity to become engineers, but still the vast majority of those don't despite the pay.
70.
▲
by
thermodynthrway
8y ago
I disagree on several points. A good chunk of why software engineers get paid well is because most people don't like writing code. It's not just because the businesses scale well, it's because it's an undesirable job for
71.
▲
by
thermodynthrway
8y ago
I make about 110k in an area with a market average of 90. I started my career at 40k around 4 years ago. Over 30% pay bump each time. Obivously, you hit dimishing returns over time, but job hopping early career has boosted my lifetime incom
72.
▲
by
thermodynthrway
8y ago
It's not a goal but it will happen because the benefits are huge. JavaScript s "tree shaking" is a joke compared to a compilers ability to remove unused code. Since it's all compiled down to WASM bytecode it's possi
73.
▲
by
thermodynthrway
8y ago
I've worked at plenty of places like this. Sales team wants another analytics WordPress plugin because they barely know how to login to the tools we already have. Slows down page loads by 50%. Sales team complains they they will lose s
74.
▲
by
thermodynthrway
8y ago
TLDR, in many situations in Illinois you make more money (due to benefits) by making less, up to a staggering income level of ~$70000 a year in some cases. I have seen this first hand. When I was broke in community college I became eligable
75.
▲
by
thermodynthrway
8y ago
It's compiled bytecode, designed to be compact. JS is "minified" but there's limits to how far you can go. JVM and WASM bytecode is designed to use as little space as possible. Not sure about WASM but the instruction set
76.
▲
by
thermodynthrway
8y ago
I appreciate the throwback to more reasonable websites, but really these days you can get something quite good with Vue. Its not hard to get a site under 200 kb. Webassembly is bound to make sites even 2-5x smaller in the near future. The r
77.
▲
by
thermodynthrway
8y ago
I've switched jobs every year and almost tripled my pay in 5 years. It's stupid to not job hop, I'm making more than twice what my friends do that have stayed put. In my experience, companies with a ton of job hoppers have b
78.
▲
by
thermodynthrway
8y ago
OMG my office might as well sponser Bose noise cancelling headphones. "Warehouse style" bare concrete on every surface. The cheapest shittiest office space for a bunch of people making 70+k a year. It's crazy. In my company e
79.
▲
by
thermodynthrway
8y ago
Good to know, would explain why there's a phantom eth port on some of these routers, must be used to connect between router and switch chips. Sounds like you're right about wifi->wired transit though if this is the casr
80.
▲
by
thermodynthrway
8y ago
You can configure FQ_Codel to match on different parts of of the packet. Default matching "tuple" for flows includes source/dest port along with source/dest IP. If you set this to source IP only it should fairly distribu
81.
▲
by
thermodynthrway
8y ago
Sometimes turning on QoS disables offload on all ports including lan. Try a download test between local machines
82.
▲
by
thermodynthrway
8y ago
I haven't seen a router under $400 that can do fair queueing in hardware faster than ~200 megabits. If you have fiber it's cheaper to setup a beefy Linux box and run PFSense on it. Hardware offload is usually disabled when you tur
83.
▲
by
thermodynthrway
8y ago
Note that if you have gigabit or faster it's usually cheaper to build a router box with a really fast CPU. Most/all reasonably priced network applicances can't do FQ in hardware offload and their CPU's are pretty weak. N
84.
▲
by
thermodynthrway
8y ago
If your network is all Linux hosts, configure BBR TCP congestion control and you won't ever have to worry about bufferbloat again (unless you use a lot of UDP) . There's a ton of research in this area, but to summarize, there'
85.
▲
by
thermodynthrway
8y ago
You can use JVM fibers now with Quasar and Comsat, and Guava provides a whole cast of immutable data structures. Direct support would be more efficient but because of Java's heavy JIT'ing you can get near native performance now
86.
▲
by
thermodynthrway
8y ago
Then, generally, give the user a bunch of filtering options and limit page depth to less than ~1000 entries
87.
▲
by
thermodynthrway
8y ago
DB has to calculate every record from 0-> offset . A user can frequently crash a server by just going to page 100+ in a big list since the database has to load all that data. Easiest way to prevent this is add enough filtering options th
88.
▲
by
thermodynthrway
8y ago
It's a bit high level to mention this, but it doesn't have the one query problem I see constantly. Paging using offset and limit. I swear every app I've worked on uses it somewhere. And it's horrifically inefficient 90%
89.
▲
by
thermodynthrway
8y ago
Californias government is almost as corrupt as Illinois and it affects everything. But the huge number of rich benefit from it too much to want any change
90.
▲
by
thermodynthrway
8y ago
I've worked with event driven architecture and it's always been a nightmare. Essentially, you're reinventing a commit log, about 1/4 of a really shitty custom database. Once you have aggregates you've basically gone
More ›