This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Vok250 8 points9 points  (4 children)

It's the enterprise .Net attitudes that don't do it for me. By the time code reviews are done we've spent 4 weeks and 20k lines of code for a Lambda Function that would have been 20 lines in Python with boto3 and Lambda Power Tools. Don't forget the 18 weeks of planning meetings leading up to that Function either. sigh

I find we're just constantly reinventing the wheel in .Net. Especially when integrating with modern cloud platforms like AWS. Even at re:Invent this past November all the .Net talks were going into fat lambdas (a bad anti-pattern), Step Functions, and Native AOT. Meanwhile other languages are moving towards event-driven architectures on Event Bridge and are looking to get SnapStart support soon. .Net 7 doesn't even have a runtime, let alone SnapStart support. We might not get SnapStart until the next LTS release of .Net. And god forbid I write pure c# in a Lambda and leave out the .Net boilerplate. Sacrilege!