Discover and read the best of Twitter Threads about #aspnet
Most recents (6)
#aspnet starter kit 🔭 - Observability
- If you can't measure it, you can't improve it.
Do you know how well your app is doing?
What's the average CPU usage, or what endpoints are called most often?
Metrics answers it all.
Let's see how we can achieve that easily 👇
#dotnet
- If you can't measure it, you can't improve it.
Do you know how well your app is doing?
What's the average CPU usage, or what endpoints are called most often?
Metrics answers it all.
Let's see how we can achieve that easily 👇
#dotnet
1\ Understanding the behavior and performance of your ASP.NET Core application are critical for ensuring its reliability and availability.
With the right tools, you can monitor key performance indicators, track error rates, and resource utilization.
With the right tools, you can monitor key performance indicators, track error rates, and resource utilization.
2\ So what to measure exactly? 🤔
Everything. Any data can be viable and bring unique tech and business insights:
- System resources: RAM, CPU, Network, Disk, etc
- Endpoints: throughput, response time, error rate
- Status codes: 200, 500, etc
- Validation errors
Everything. Any data can be viable and bring unique tech and business insights:
- System resources: RAM, CPU, Network, Disk, etc
- Endpoints: throughput, response time, error rate
- Status codes: 200, 500, etc
- Validation errors
#aspnet starter kit 🚨 - Monitoring
You've got health checks in place. With just one HTTP call you can check if an app is healthy.
So how do you make it automatic, so you'll be the first to know if the system goes down?
Let's explore monitoring and alerts. 👇
#dotnet
You've got health checks in place. With just one HTTP call you can check if an app is healthy.
So how do you make it automatic, so you'll be the first to know if the system goes down?
Let's explore monitoring and alerts. 👇
#dotnet
1\ With the rise of distributed systems, it's increasingly important to have a robust monitoring solution in place. Health checks allow you to monitor the health of your apps and detect any issues before they escalate.
And then it has to be monitored all the time.
And then it has to be monitored all the time.
2\ The benefits of continuous monitoring and alerting are numerous. It allows you to detect issues early, minimize downtime, and improve user experience. It also helps you respond quickly to incidents and resolve them before they become bigger problems.
🤔 How do you currently solve #authentication?
Here’s a summary of #AuthN solutions from this #HackerNews thread:
news.ycombinator.com/item?id=221571…
👇👇👇
Here’s a summary of #AuthN solutions from this #HackerNews thread:
news.ycombinator.com/item?id=221571…
👇👇👇
#Firebase Auth
- Free
- Scalable
- Easy to get up & running
- Good docs
- Social auth
- Integrate with any OAuth system via custom tokens
- Email verification
- SMS auth, passwordless login (“magic links”)
- SDK’s for different languages
@Firebase | firebase.google.com/docs/auth
🔗
- Free
- Scalable
- Easy to get up & running
- Good docs
- Social auth
- Integrate with any OAuth system via custom tokens
- Email verification
- SMS auth, passwordless login (“magic links”)
- SDK’s for different languages
@Firebase | firebase.google.com/docs/auth
🔗
#KeyCloak by @RedHat
- Open source
- Social auth, SSO
- Good docs & support
- Easy deploys within a #Docker container
- OAuth2, OIDC, SAML, MFA, themes, & more
@keycloak | keycloak.org
🔗
- Open source
- Social auth, SSO
- Good docs & support
- Easy deploys within a #Docker container
- OAuth2, OIDC, SAML, MFA, themes, & more
@keycloak | keycloak.org
🔗
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.
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!
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.
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
- 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 openid.stackexchange.com 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
- The rest of the teams are progressing on other work while we advance the .NET Core initiative
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.
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.
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 raw...it 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.
