2 ms·
I think it's partly a hat-tip to ISVs using .NET. Entity Framework (Core and Desktop) works best with SQL Server, with whole .NET Core is cross-platform thing t
by taspeotis 9y ago
I think it's partly a hat-tip to ISVs using .NET. Entity Framework (Core and Desktop) works best with SQL Server, with whole .NET Core is cross-platform thing they let ISVs sell to Linux shops too. The alternative would be to mix EF with PostgreSQL or (horror of horrors) MySQL which is a pain-in-the-ass for testing/QA. ORMs are leaky abstractions!
If you're ponying up for a SQL Server license you can afford to pony up for the Windows license. But if you're not a Microsoft shop and you're buying .NET Core-based COTS you can skip the license fees and install SQL Server vNext Express on your Linux machines. (Up to the point where you max out Express and have to cough up for Standard anyway.)
- jmkni 9y agoAt our place, we use ServiceStack with OrmLite, which runs well on .net core and plays nicely with MySQL. You can switch between SQL Server and MySQL by changing just one line of code.
- martinald 9y agoYes, I also love OrmLite. It's so good and I miss it when doing dev in other languages, and as you say works perfectly across different SQL backends (unlike EF which tends to blow up horribly at the worst possible time with some obscure bug).
- j_s 9y agoSo it is worth $250/seat + $175/yr renewal? I haven't looked at much ServiceStack stuff because of the cost.
- jmkni 9y agoWell I'm the only dev at the moment so I really just need an indie dev license for myself, and it's licensed per developer, not per project etc. I think it's worth it. In my opinion, anybody working on .net ends up spending a lot of time writing what is essentially their own version of ServiceStack, on Web API. It has a lot of features that you would end up writing anyway, spend months doing so, and would probably do less well. It basically gives you a massive head start.