To clarify, my point is that the marginal effort in getting to intermediate scales (say 1000 users) is almost the same as getting to maximal scale, since higher orders of scaling are mostly handled by infrastructure that's mostly agnostic to the specifics of the codehttps://twitter.com/vgr/status/1096234854000152577 …
-
-
Also, I think the breakpoint where scale effects kick-in is not 10, but whatever is the max the programmer can personally support/troubleshoot on a bespoke basis. When complexity forces you to switch from managed to DIY/automated service provisioning.
-
Serverless has the same scaling properties. It's just a function that runs as many times as it's needed
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.