stevencorona
Joined 15 years ago
Joined 15 years ago
This has been a really elegant and low-complexity way to get distributed pubsub without the complexity of running a distributed erlang cluster (which seems a lil bit painful in a K8S+Continuous Deploy world)
There -are- some big downsides to be aware of though.
1. You can't use PgBouncer w/ LISTEN/NOTIFY. This has been really painful because of the high memory overhead of a pgsql connection + elixir keeping a pool of open pgsql connections. The tried and true method of scaling here is to just use PgBouncer. We've kicked the can on this by vastly over-provisioning our pg instance, but this has cost $10s of thousands on the cloud. Of course, it's solvable (dedicated non-pgbouncer connection pool just for LISTEN/NOTIFY, for example), but painful to unwind.
2. The payload has a fixed size limit (8KB, IIRC). This has bitten us a few times!
Even though I really like pg_notify, I think that if I were starting over, I'd probably just use Redis Pub/Sub to accomplish the same thing. Tad bit more complex if you're not already running Redis, but without the downsides. (Of course, w/ Redis, you don't get the elegance of firing a notification via a pg trigger)
In the early days, quota increases felt like a formality - put in a request and they’d get approved a few minutes later. Sometimes it was a bit of a puzzle (you can’t increase X unless you also know to ask for Y) - but never a roadblock.
Over the past 2-3 years, I’ve starting having the experience of having a quota increase denied and having a helpful account manager insist we jump on a call to get the quota increase. I’m not talking about anything crazy either - like maybe going from an existing 72 vCPU quota to 144.
Doesn’t make me feel very confident that I’d actually be able to use the cloud to actually do cloudy things in a pinch, like bursty on-demand scaling
They had a really wild architecture with FPGAs that, if I remember correctly, sat in between the CPU/disk and was used to offload some of query execution.
It was wildly expensive + expensive to maintain, so the company ended up (unsuccessfully, I think) jumping to Hadoop. Crazy times :)
One of my current frustrations is the inability, out-of-the-box, to write to sessions from LiveView. I understand the reason why, but I personally find the "redirect to a controller to set the cookie" pattern to be a bit hacky and more work than I'd like in order to just.. set a cookie.
I hope that a future release has a built-in pattern for writing sessions and cookies in general.
Why has HiDPI has stagnated outside of the apple ecosystem?
For the most part, daily driving Linux as my desktop has been great - no small thanks to Electron. Slack, Spotify, VSCode, etc. all just mostly work.
Going the arch-route took extra upfront work since you're effectively building a desktop environment from scratch, but the benefit is knowing exactly how -everything- works. If I press my "volume up" shortcut and the overlay volume bar isn't displayed, I know exactly which sway config and executable to look at. It's refreshingly simple.
The downsides are that upgrading is a bit anxiety producing (will I break anything?). HiDPI on Linux is still (in my experience) a bit of a mess. If you run wayland, you need to patch xwayland/sway/wlroots if you don't want blurry x11 apps. And there are some quirks- like, I can't drag files into Slack. Maybe it's fixable, but at some point you become satisfied with "good enough".
This brings me hope. But only a little. I’m sure they’ll find a way to keep running it.
The Tesla Supercharging experience has been pretty great. The route planner calculates charging stops automatically and you only need to wait 5-10 mins to top off ~100 miles before you're back on the road.
Without the Superchargers, though, the experience would be pretty terrible - how is the current charging station grid for non-Tesla EVs?
Besides the (now discontinued) Planar IX2790, which had severe quality control issues (went through 4- all with major dead pixels and burn-in), I don’t think there are any readily available DisplayPort-based 5K monitors out there :(
Feels like hidpi displays have pretty much stagnated outside of apple ecosystem
[ my public key: https://keybase.io/stevencorona; my proof: https://keybase.io/stevencorona/sigs/rK_5YI7sBRTt3uHVXBDtP6ZTEQNvn9s0E7ovxteV4U8 ]