El motor de base de datos también define tu ORM.
Si voy por MariaDB, Dapper es mi opción. Con SQL Server, elijo Entity Framework o Dapper según las necesidades de control del proyecto.
¿Qué ORM prefieres con tu BD?
#MariaDB#SQLServer#Dapper#EntityFramework
The C# approach is the same async use case that Java has given up on. It’s a more complicated programming model, but it does increase concurrency allowing those C# programs to handle a larger load.
But the tradeoff is still the same. Those C# programs are much slower than they could be, and thanks to EntityFramework presses against memory limitations rapidly as the system scales up. (A consequence of the serial nature of processing.)
It’s not unique to C#, mind you. That’s the same reason Java Spring apps require so much memory.
In comparison, a pipelined approach can reliably operate at high traffic loads with only ~512MB of memory and faster response times. (My customers see a stable 200-300mb runtime. Much better than the PHP/Wordpress and C# systems they replaced.)
Trabajé en una startup donde dejaban que el ORM gestionara la base de datos.
Si un dev necesitaba una columna, la agregaba al modelo y dejaba que la 'magia' ocurriera.
Cada dev hacía lo que quería; cuando supe esto, generé el diagrama de la base de datos y era algo como esto:
📝 Your daily dose of .NET is here! Issue #399 covers federating databases with Data API Builder 🔗, the official arrival of the .NET 11 Preview 1 🚀, a guide to "explained without fear" synchronization primitives 🔒, and how to stop using try-catch in every controller 🛑. Time to sharpen your .NET expertise! 👇
dotnetnews.co/archive/the-ne…#dotnet#csharp#dotnet11#entityframework#performance