Memory usage of a toy C# server and client with 500K concurrent connections on

Re:Memory usage of a toy C# server and client with 500K conc... by naasking on Sunday January 27, 2019 @09:24AM (#19011780)

> I find writing raw SQL to be quite annoying for simple CRUD operations. It's just so easy to make stupid little syntax mistakes when writing SQL.

There are ways to mitigate this [1]. You write your queries in .sql files in Visual Studio, so you get intellisense and syntax highlighting, and you can even add these to your automated test suite to ensure they run correctly.

[1] https://github.com/naasking/Dapper.Compose

[ Parent | on HN ]

Re:Memory usage of a toy C# server and client with 500K conc... by platz on Sunday January 27, 2019 @12:30PM (#19012684)

what is the benefit of "composing" queries via this library instead of just running them separately in a single connection? The "composed" queries are completely opaque to each other and are independent - they are not "composed", just "batched".

[ Parent | on HN ]

Re:Memory usage of a toy C# server and client with 500K conc... by naasking on Sunday January 27, 2019 @03:02PM (#19013493)

> what is the benefit of "composing" queries via this library instead of just running them separately in a single connection?

I think the link is pretty clear: it combines and batches queries while providing a type-safe interface for the returned results. It further provides intellisense and unit testing features that are tedious and error-prone to achieve in other ways.

Of course you can do this all by hand, or manually batch your queries to avoid round trips, but why would you want to?

[ Parent | on HN ]