> ... load balancers, iptables, and other physical system tasks I think one point of the article is that if you have a big system you don't need load-balancer

> ... load balancers, iptables, and other physical system tasks I think one point of the article is that if you have a big system you don't need load-balancers or worry much about routing etc. The assumption also I think is that you have "one app" which you offer to the public. Now on such a big system it might of course make sense to implement parts of the application as "serverless". When you have just one server (or 2, app and database) it is pretty much the same conceptually AS "serverless" since you don't need to worry about multiple servers when you don't have multiples of them.