home.social

#aspnetcore — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #aspnetcore, aggregated by home.social.

  1. Modernizing .NET Part 26! 🛡️

    Today we’re implementing the Rate Limiting Middleware in ASP.NET Core.

    ✅ Concurrency control
    ✅ Stable response times under load
    ✅ No more cascading failures

    medium.com/@michael.kopt/%EF%B

  2. Modernizing .NET Part 26! 🛡️

    Today we’re implementing the Rate Limiting Middleware in ASP.NET Core.

    ✅ Concurrency control
    ✅ Stable response times under load
    ✅ No more cascading failures

    medium.com/@michael.kopt/%EF%B
    #dotnet #csharp #dotnetcore #aspnet #aspnetcore #ratelimiting #performance

  3. I’m speaking at VSLive! is sunny San Diego this Sept 14-18.

    Through hands-on labs, deep-dive workshops & practical technical sessions, you explore the latest advancements in modern #dotnet, #ASPNETCore, Azure, AI-powered development, GitHub Copilot, Blazor, .NET MAUI, Kubernetes, and modern data platforms.

    Register by July 17th & use my discount code. You save $500 off the standard rate!

    Learn more & register at vslive.com/sandiego

  4. Modernizing .NET Part 25! 🛡️

    Today we’re talking about rate limiting as a safety mechanism.

    ✅ Prevent CPU thrashing
    ✅ Manage concurrency correctly
    ✅ Controlled degradation vs. catastrophic failure

    medium.com/@michael.kopt/%EF%B

  5. Modernizing .NET Part 25! 🛡️

    Today we’re talking about rate limiting as a safety mechanism.

    ✅ Prevent CPU thrashing
    ✅ Manage concurrency correctly
    ✅ Controlled degradation vs. catastrophic failure

    medium.com/@michael.kopt/%EF%B
    #dotnet #aspnet #dotnetcore #aspnetcore #csharp #programming #performance

  6. Modernizing .NET Part 25! 🛡️

    Today we’re talking about rate limiting as a safety mechanism.

    ✅ Prevent CPU thrashing
    ✅ Manage concurrency correctly
    ✅ Controlled degradation vs. catastrophic failure

    medium.com/@michael.kopt/%EF%B
    #dotnet #aspnet #dotnetcore #aspnetcore #csharp #programming #performance

  7. Modernizing .NET Part 25! 🛡️

    Today we’re talking about rate limiting as a safety mechanism.

    ✅ Prevent CPU thrashing
    ✅ Manage concurrency correctly
    ✅ Controlled degradation vs. catastrophic failure

    medium.com/@michael.kopt/%EF%B
    #dotnet #aspnet #dotnetcore #aspnetcore #csharp #programming #performance

  8. Modernizing .NET Part 25! 🛡️

    Today we’re talking about rate limiting as a safety mechanism.

    ✅ Prevent CPU thrashing
    ✅ Manage concurrency correctly
    ✅ Controlled degradation vs. catastrophic failure

    medium.com/@michael.kopt/%EF%B
    #dotnet #aspnet #dotnetcore #aspnetcore #csharp #programming #performance

  9. More tuning the of performance path in StyloBot at the moment.

    mostlylucid.net/blog/stylobot-

    (It's the free, open source bot detection engine I'm building)

    This part is about making repeat traffic cheaper to process without turning the cache into a permanent source of wrong answers.

    That means boring but important mechanisms:

    EWMA updates

    hysteresis thresholds

    verdict caching

    variance watchdogs

    bounded memory

    refresh sampling

    I'm not an ML guy, but a lot of this maps neatly onto ML and control theory ideas once you start writing it down.

    The useful pattern is simple enough:

    learn from traffic, make the common path faster, keep enough uncertainty in the system that it can recover when the world changes.

    The next post in the StyloBot release series is a deep dive into that mechanism.

    Very much one for the nerds.

    In .NET so...kinda niche...ML / AI ...

    mostlylucid.net/blog/stylobot-

    #dotnet #opensource #aspnetcore #performance #systemsdesign

  10. More tuning the of performance path in StyloBot at the moment.

    mostlylucid.net/blog/stylobot-

    (It's the free, open source bot detection engine I'm building)

    This part is about making repeat traffic cheaper to process without turning the cache into a permanent source of wrong answers.

    That means boring but important mechanisms:

    EWMA updates

    hysteresis thresholds

    verdict caching

    variance watchdogs

    bounded memory

    refresh sampling

    I'm not an ML guy, but a lot of this maps neatly onto ML and control theory ideas once you start writing it down.

    The useful pattern is simple enough:

    learn from traffic, make the common path faster, keep enough uncertainty in the system that it can recover when the world changes.

    The next post in the StyloBot release series is a deep dive into that mechanism.

    Very much one for the nerds.

    In .NET so...kinda niche...ML / AI ...

    mostlylucid.net/blog/stylobot-

    #dotnet #opensource #aspnetcore #performance #systemsdesign

  11. More tuning the of performance path in StyloBot at the moment.

    mostlylucid.net/blog/stylobot-

    (It's the free, open source bot detection engine I'm building)

    This part is about making repeat traffic cheaper to process without turning the cache into a permanent source of wrong answers.

    That means boring but important mechanisms:

    EWMA updates

    hysteresis thresholds

    verdict caching

    variance watchdogs

    bounded memory

    refresh sampling

    I'm not an ML guy, but a lot of this maps neatly onto ML and control theory ideas once you start writing it down.

    The useful pattern is simple enough:

    learn from traffic, make the common path faster, keep enough uncertainty in the system that it can recover when the world changes.

    The next post in the StyloBot release series is a deep dive into that mechanism.

    Very much one for the nerds.

    In .NET so...kinda niche...ML / AI ...

    mostlylucid.net/blog/stylobot-

    #dotnet #opensource #aspnetcore #performance #systemsdesign

  12. More tuning the of performance path in StyloBot at the moment.

    mostlylucid.net/blog/stylobot-

    (It's the free, open source bot detection engine I'm building)

    This part is about making repeat traffic cheaper to process without turning the cache into a permanent source of wrong answers.

    That means boring but important mechanisms:

    EWMA updates

    hysteresis thresholds

    verdict caching

    variance watchdogs

    bounded memory

    refresh sampling

    I'm not an ML guy, but a lot of this maps neatly onto ML and control theory ideas once you start writing it down.

    The useful pattern is simple enough:

    learn from traffic, make the common path faster, keep enough uncertainty in the system that it can recover when the world changes.

    The next post in the StyloBot release series is a deep dive into that mechanism.

    Very much one for the nerds.

    In .NET so...kinda niche...ML / AI ...

    mostlylucid.net/blog/stylobot-

    #dotnet #opensource #aspnetcore #performance #systemsdesign

  13. More tuning the of performance path in StyloBot at the moment.

    mostlylucid.net/blog/stylobot-

    (It's the free, open source bot detection engine I'm building)

    This part is about making repeat traffic cheaper to process without turning the cache into a permanent source of wrong answers.

    That means boring but important mechanisms:

    EWMA updates

    hysteresis thresholds

    verdict caching

    variance watchdogs

    bounded memory

    refresh sampling

    I'm not an ML guy, but a lot of this maps neatly onto ML and control theory ideas once you start writing it down.

    The useful pattern is simple enough:

    learn from traffic, make the common path faster, keep enough uncertainty in the system that it can recover when the world changes.

    The next post in the StyloBot release series is a deep dive into that mechanism.

    Very much one for the nerds.

    In .NET so...kinda niche...ML / AI ...

    mostlylucid.net/blog/stylobot-

  14. Modernizing .NET Part 24! 📊
    Today we’re implementing modern observability with Prometheus and Grafana.
    ✅ OpenTelemetry metrics
    ✅ Runtime health (GC, Threads)
    ✅ Kubernetes-native monitoring
    medium.com/@michael.kopt/moder
    #dotnet #csharp #aspnet #aspnetcore #csharp #prometheus #grafana #monitoring

  15. Modernizing .NET Part 24! 📊
    Today we’re implementing modern observability with Prometheus and Grafana.
    ✅ OpenTelemetry metrics
    ✅ Runtime health (GC, Threads)
    ✅ Kubernetes-native monitoring
    medium.com/@michael.kopt/moder
    #dotnet #csharp #aspnet #aspnetcore #csharp #prometheus #grafana #monitoring

  16. Modernizing .NET Part 24! 📊
    Today we’re implementing modern observability with Prometheus and Grafana.
    ✅ OpenTelemetry metrics
    ✅ Runtime health (GC, Threads)
    ✅ Kubernetes-native monitoring
    medium.com/@michael.kopt/moder
    #dotnet #csharp #aspnet #aspnetcore #csharp #prometheus #grafana #monitoring

  17. Modernizing .NET Part 24! 📊
    Today we’re implementing modern observability with Prometheus and Grafana.
    ✅ OpenTelemetry metrics
    ✅ Runtime health (GC, Threads)
    ✅ Kubernetes-native monitoring
    medium.com/@michael.kopt/moder
    #dotnet #csharp #aspnet #aspnetcore #csharp #prometheus #grafana #monitoring

  18. Modernizing .NET Part 24! 📊
    Today we’re implementing modern observability with Prometheus and Grafana.
    ✅ OpenTelemetry metrics
    ✅ Runtime health (GC, Threads)
    ✅ Kubernetes-native monitoring
    medium.com/@michael.kopt/moder

  19. That while + Task.Delay loop is quietly drifting. This drop swaps in PeriodicTimer to keep background jobs on time and spotlights IdentityServer rate limits, cleaner Minimal APIs, and YARP as a lean gateway. #dotnet #csharp #aspnetcore

    .NET drip - Saturday, May 9, 2...