> Is it because of the deployment overhead or something else?
In my experience, two things. Smaller is the JIT overhead. Bigger, is the haphazardishness of the other AWS Libraries for .NET; there's sometimes 'edge cases' where if running in a lambda, you have to do something special, set a special flag, etc. And often the solution is buried in a SO post or closed github issue.
Have you researched into .NET Core Function Apps?
Re:AWS Lambda adds supports for .NET 6
by RedWarrior on Monday February 28, 2022 @02:37AM
(#30497352)
Which hurdles are you facing when transitioning from framework to core?
I've inherited a pretty big C# project at work and we've just started porting it from Framework to Core. Definitely feels like there are some opportunities for serverless in there.