Ask HN: Does anyone else find the AWS Lambda developer experience frustrating?
&quot;Think of the history of data access strategies to come out of Microsoft. ODBC, RDO, DAO, ADO, OLEDB, now ADO.NET – All New! Are these technological imperatives? The result of an incompetent design group that needs to reinvent data access every goddamn year? (That’s probably it, actually.) But the end result is just cover fire. The competition has no choice but to spend all their time porting and keeping up, time that they can’t spend writing new features. Look closely at the software landscape. The companies that do well are the ones who rely least on big companies and don’t have to spend all their cycles catching up and reimplementing and fixing bugs that crop up only on Windows XP.&quot; - Fire And Motion, Joel on Software<p>In my own work with serverless I think about this a lot. In my day job, we built a new service and we pay AWS a few dollars per month to run. It would have cost us around $100 a month in AWS costs. However, the operational complexity is extremely high and we are also coupled to another service via Kinesis. For a billion dollar business, the trade off doesn&#x27;t seem worth it.<p>I wonder how much of serverless is just AWS firing at Google (and Heroku, DO, etc) and other competitors. It certainly hasn&#x27;t made my life as a developer easier. It&#x27;s certainly much cheaper for some use cases but the complexity of the system goes up very quickly, and you&#x27;re end up having to manage a lot of that complexity using an inferior tool like Cloud Formation (or Terraform).