When does this hurt your scaling ability? From my experience, scaling a typical site has always been bottlenecked in the database. http workers are generally s

When does this hurt your scaling ability? From my experience, scaling a typical site has always been bottlenecked in the database. http workers are generally stateless and easily scalable. Where it gets tricky is optimizing the database reads, caching, and invalidation. Is the intended use case just simple CRUD of data that it not under extreme read or write loads? It seems like you could quickly build CRUD for tables in _language of choice_ and still have the ability to optimize reads with caching later..