I don't think there is a generic answer to this. It mostly depends on the startup size, their legal team and the team's. I have seen quite a few hire outside US, and then there obviously are startups outside the US that YC funds too.

Ha, I know. It's a single VM instance right now. I have been thinking of migrating to Gatsby for quite some time now. This unexpected traffic and the server limitations give me a reason to get working on it!

Or you could serve a fully static site with vanilla JS.

vanilla JS might be too much to maintain. I have already started working on the Gatsby version and will try and accelerate that.

I mean generating your HTML on the server. If you use HTML as a semantic markup language, it works pretty well. Then, using Vanilla JS for the interactivity. I doubt it's "too much to maintain"- what is harder in Vanilla JS than Gatsby?

You can write much of your site in raw HTML. For example, your right panel– you can write it in raw HTML, annotate it with some tags. Make it an iframe, just use CSS to get rid of the borders, or an XMLHTTPRequest. As long as you make good use of CSS, you can have a few tags and it'll work.

Concepts are definitely transferrable across domains. And then adapted according to desired outputs. Cost of performance is interesting and somewhat similar to the least-time approach but adapted to the supercomputers domain.

We all learn everyday. I am learning from the comments here as well. The best we can do is accept we were wrong and correct it.

Added least time to the post as well. Thank you!

Thank you. I am not sure how to introduce transit and the concept of hops in an introductory post without explaining in depth about the networking side of it. Maybe you could help me out with that?

I’d think it’s fine to be hand-wavy:

Load balancing isn’t just about server load or congestion, it’s also about network load and congestion. If a web page or video takes longer for a user to download, it ties up the server longer too.[1]

Load balancing algorithms can also consider network paths or round trip times between the user and a server to give users a faster web download or video stream. To do this, they may use information from network routing topology, such as how many “hops” or routers between the user and the server, or may even triangulate actual network performance by assessing measurements from multiple data centers and load balancing to the most responsive.

1. See “snoshy” comment on latency in these comments: https://news.ycombinator.com/item?id=25920284 — roughly, you aim to avoid queuing or connection creep, as you mentioned in the intro, and speed of opening, transmitting data over, then closing the connection, can make a huge difference.

I know about the caching issue is a little trivial but it was worth mentioning. Though I should have mentioned the low TTL piece. I will add that to the post. And also will add the health check part too. Reading up a bit about it. Thanks for the information!

Haha, you can treat yourself on becoming a multi-tasking procrastinator for putting off a bunch of shit at the same time!

Sorry about that. Apparently someone was DDOSing as soon as this started getting some traffic. It is back now. Working on putting in better configurations to prevent that from happening in the future.

That sucks. #hugops. No worries. Good luck. Thanks for the article.

Thanks for the support.

Here's an awesome video from the library author explaining a bit more about Recoil from today's React Europe live stream if anyone is interested: https://www.youtube.com/watch?v=_ISAA_Jt9kI.