Discover and read the best of Twitter Threads about #aspnet

Most recents (3)

We're trying to repro an error we can only catch in production under extreme load (after many hours of hunting). I'm about to re-enable the problematic server now to get a dump.

You few hundred users who are about to get 500s, we salute you for your sacrifice.
Update: we haven't found the *exact* issue but we found super curious details which tremendously narrowed it down (exact route) and a mitigation. We'll try to repro and eliminate the cause, but have a workaround for anyone on-call now as well.

Your sacrifice is appreciated!
If you're curious, we have this rare (once every ~ 2 weeks) issue where our connection pool (150 max) fills up and *never* releases. We can take the server out for an hour, it'll come back still full. The 150 never let go. The connections are lost in the ether for some reason.
Read 9 tweets
Oh hey, we haven't talked about .NET Core in a while. We've been making some progress, here's what's been going on over at Stack Overflow...
- @marcgravell and I shipped SE.Redis v2.0
- I'm porting everything to EF Core (not 100% yet)
- @m0sa has been working on MoonSpeak (localization) and performance with Marc
- @deanward81 has been tearing out loads of old email code to finish the StackMail migration
@marcgravell @m0sa @deanward81 - @kevinmontrose has been suffering through auth code to deprecate and move us to all-OAuth (and simplify things), allowing us to kill DotNetOpenAuth usage.
- The rest of the teams are progressing on other work while we advance the .NET Core initiative
Read 19 tweets
Been asked several times this week about "right tool for the right job". Do I believe in it? Absolutely.

I help maintain Dapper, the most popular third party ORM in .NET, yet I'm contributing to EF Core at the moment. The goal is helping developers; both tools do that.
Some people like raw SQL, ultimate flexibility, and things generated SQL can't sanely do. We do. We built Dapper around it.

Some people like easier development and data models, EF Core is for them.

These aren't distinct groups. We're about to be using *both* at Stack Overflow.
When someone asks about inserting object graphs which have rows across several tables and want to do it all sounds great, **if it stays simple**. When it gets complex: you're basically then building a data context. We would be. But why? EF Core exists. We'll use it.
Read 10 tweets

Related hashtags

Did Thread Reader help you today?

Support us! We are indie developers!

This site is made by just three indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3.00/month or $30.00/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!