3 ms·
Is it because of the deployment overhead or something else? I've inherited a pretty big C# project at work and we've just started porting it from Framework to
by jcims 5y ago
Is it because of the deployment overhead or something else?
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.
- DeWilde 5y agoHave you researched into .NET Core Function Apps?
- RedWarrior 5y agoWhich hurdles are you facing when transitioning from framework to core?
- to11mtm 5y ago> 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.