4 ms·

Thanks for the write up. We evaluated ServiceStack and the license conditions, lock in risk and cost for a supported product across our estate was prohibitive.

by setquk 9y ago

Thanks for the write up. We evaluated ServiceStack and the license conditions, lock in risk and cost for a supported product across our estate was prohibitive. The only desirable feature was Redis sentinel but we can live without that. Honestly we can just switch parts of the system to another platform for the same cost and get an ROI over a couple of years.

mythz 9y ago
Understood, although I still think you should consider evaluating .NET Core (even w/o ServiceStack), the latest .NET Standard 2.0 offers a broad and compatible API Surface shared by .NET Framework v4.6.2 and .NET Core. The new msbuild project format is much more human-friendly that together with tools like `dotnet watch run` you can for the first time productively develop C# Apps with command-line tooling and a text editor like VS Code in any OS (that also sports IDE features like intelli-sense/debugging/etc - tho Rider is my personal pref / with VS Code for the SPA front-end). Being able to deploy to Linux opens up a new world of automation possibilities where you have first-class Docker support or can incrementally deploy just changed files in seconds with a single rsync + ssh supervisord bash command run with WSL - everything feels cleaner, faster and more automatable and runs flawlessly cross-platform, e.g. all our .NET Core Apps are developed on Windows and deployed to Linux. It's a different world with a much improved development model that I find vastly superior compared to traditional classic ASP.NET Framework Web Apps - which I don't see myself ever creating greenfield Apps for again.