<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>ledauphin</author><text>What you (and many others here) are objecting to is completely orthogonal to serverless as an architecture.&lt;p&gt;There&amp;#x27;s nothing about serverless that requires separate repositories or even microservices. I know because I have built a 50,000 line serverless application that is a single repository and deploys functionally as a monolith.&lt;p&gt;We also don&amp;#x27;t use step functions heavily, because, like you say, that&amp;#x27;s basically a cloud-specific DSL that you could write in a real programming language with only slightly worse visibility.&lt;p&gt;Serverless is, plain and simple, about passing immutable &amp;quot;partial computation&amp;quot; state through events and keeping all mutable long term state in a database.</text><parent_chain><item><author>zimbatm</author><text>Please don&amp;#x27;t do this.&lt;p&gt;I have seen this in practice. A simple CRUD app split across literally 100 of &amp;quot;re-usable&amp;quot; repositories. The business logic is all over the place and impossible to reason about. Especially with step-functions, now the logic is both in the code and on the cloud-level. Each developer gets siloed into their little part and not able to run the whole app locally.&lt;p&gt;The whole thing could easily fit in a single VM as a Rails or Django application.&lt;p&gt;The only one that will be happy about this is AWS and contractors because it&amp;#x27;s a guaranteed lock-in.</text></item></parent_chain></comment><story><title>What a typical serverless architecture looks like in AWS</title><url>https://medium.com/serverless-transformation/what-a-typical-100-serverless-architecture-looks-like-in-aws-40f252cd0ecb</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>api</author><text>The whole &amp;quot;serverless&amp;quot; fad is about lock-in.&lt;p&gt;I also really wish they would not have squatted that term. It should refer to decentralized P2P systems which are truly serverless.</text><parent_chain><item><author>zimbatm</author><text>Please don&amp;#x27;t do this.&lt;p&gt;I have seen this in practice. A simple CRUD app split across literally 100 of &amp;quot;re-usable&amp;quot; repositories. The business logic is all over the place and impossible to reason about. Especially with step-functions, now the logic is both in the code and on the cloud-level. Each developer gets siloed into their little part and not able to run the whole app locally.&lt;p&gt;The whole thing could easily fit in a single VM as a Rails or Django application.&lt;p&gt;The only one that will be happy about this is AWS and contractors because it&amp;#x27;s a guaranteed lock-in.</text></item></parent_chain></comment><story><title>What a typical serverless architecture looks like in AWS</title><url>https://medium.com/serverless-transformation/what-a-typical-100-serverless-architecture-looks-like-in-aws-40f252cd0ecb</url></story>