Serverless Is An Architectural Handicap (And I'm Tired of Pretending it Isn't)
Serverless Is An Architectural Handicap (And I'm Tired of Pretending it Isn't)
Serverless Is An Architectural Handicap (And I'm Tired of Pretending it Isn't)

Serverless Is An Architectural Handicap (And I'm Tired of Pretending it Isn't)
Serverless Is An Architectural Handicap (And I'm Tired of Pretending it Isn't)

My app went from a single code base that handles a million different actions to a million code bases that each handle a single action, but they still all depend on each other and still are tightly coupled, but now they're spread out across 50 disparate cloud services so maintenance effort only got worse.
"We can solve any problem by introducing an extra layer of abstraction. Except for the problem of too many layers of abstraction."