ahuang

13 ms·

1.
Migrating to Pulumi(airplane.dev)
3 points by ahuang 4y ago|0 comments
2.
by ahuang 6y ago
(I work at Quill). We've found threading to work really well with teams as small as 3. (2, probably not.) In professional contexts, conversations tend to be about specific topics -- someone posts a GitHub issue, bug report, feature dis
3.
by ahuang 6y ago
(I work at Quill.) Quill definitely has some similarities to a forum/message board in that it's slightly more structured -- but it's very much chat at it's core. What we've found is when a group gets large and/
4.
by ahuang 6y ago
> Your regular conversations are absolutely yours -- your messages by default are encrypted in transit and at rest. (I work at Quill too). Yes, absolutely! That is just table stakes when it comes to security for your messaging experience
5.
by ahuang 7y ago
I think the main issue is it seems really one-sided and the intent was to be snarky, vs educational. I posted a comment here detailing some ways to work around some of the pitfalls. I think if she devoted more time in the article to solutio
6.
by ahuang 7y ago
I think this conflates a poor implementation of a webserver with python/gunicorn/gevent being bad. There are a few (easy) things to do to avoid some of the pitfalls she encountered: > A connection arrives on the socket. Linux r
7.
by ahuang 7y ago
Not always ;). As someone with experience managing mongo at scale, this really speaks volumes to the amount of effort needed to make it not do the wrong thing. And even then, there are unknown unknowns like this that can pop up at any time.
8.
by ahuang 7y ago
gRPC isn't a requirement for response streaming (as is quoted as one of the main reasons for doing the migration). That can all be achieved with http/json using chunked encoding. In fact, that's what the gRPC-gateway (http&#x
9.
Katalog-Sync: Reliable Integration of Consul and Kubernetes(medium.com)
2 points by ahuang 8y ago|0 comments
10.
by ahuang 10y ago
Generally its the upper 32k ports that are ephemeral, and if your churn more than that per minute in connections, you'll run into that TIME_WAIT issue. Hacky way to get around that is to enable tcp_tw_reuse which will let you reuse por