Menu

1 / 3

Keeping the Data Where It Is, Modernizing Only the App From .NET Framework to Lambda — What Changes and What Does Not (A 1-Environment Test)

DEV Community: dotnet·Yoshiki Fujiwara(藤原 善基)@AWS Community Builder·about 16 hours ago
#fmNBVtvW
#devtodotnet#devto#dev#volume#access
Reading 0:00
15s threshold

Keeping the data you already have, modernizing only the app — what changes across SMB, NFS, and S3 Access Points

Business apps written for .NET Framework are still running in many Windows environments. .NET Framework runs only on Windows, and its feature set is effectively frozen. Current .NET (modern .NET) is cross-platform: it runs on Linux, in containers, and on serverless such as AWS Lambda. Moving an app to modern .NET frees it from the OS dependency and the support-window constraint, and lets it run without an always-on server, paying only for what it uses. Microsoft itself frames the move from .NET Framework to modern .NET as a good opportunity to containerize and go cloud-native ( Microsoft Learn: Upgrade .NET apps overview ).

But work usually stalls on the same question: the app can move, but what about the data the app has been reading and writing?…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.