(Mux co-founder here) The Postgres system described as the predecessor to Clickhouse here actually was cstore_fdw with a pretty heavily customized (and outdated ) CitusDB. CitusDB is a great system for sharding and distributing postgres, but we found that the compression and query performance for this specific analytics use case was much better served by Clickhouse.
HN user
A-F1V3
[ my public key: https://keybase.io/a_f1v3; my proof: https://keybase.io/a_f1v3/sigs/gOB_LtDN8bBgVr2Knrm4p_xkIMyfLvn1GiYRb76NvgE ]
If you are open to using an (awesome) vendor for this kind of thing, I would highly recommend taking a look at Backplane (https://www.backplane.io/). It's as simple as running a sidecar Backplane agent container along side any container that you want to route http traffic to and then shape the traffic via their API (it becomes your load balancer as well). They automatically provision Lets Encrypt certificates for your endpoints as well, so you don't have to worry about any of that. We have been using it at Mux in production for months and have been very happy with the results. Backplane also has some other nice built in features like blue/green deploys and built in OAuth support that are really nice to have out of the box.
Right! From the description:
"Ever had those moments when you just open a new tab of your favorite social media site over and over again?"
Literally how I just ended up finding this link...
That WhatsApp vs Telegram user comparison is interesting... nearly everyone in my social group uses Telegram, I don't think I've ever even installed WhatsApp. I know WhatsApp has significantly more users worldwide, but for whatever reason my tribe has chosen Telegram.
I tried the consumer version while wearing glasses a few weeks ago. No lenses were changed out and the device just sat over top of the glasses, it was fairly comfortable but I only spent less than 5 mins with it on.
Daala can't get here fast enough.