home.social

Search

1000 results for “aspnes”

  1. 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

  2. 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

  3. 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

  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
    #dotnet #aspnet #dotnetcore #aspnetcore #csharp #programming #performance

  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. Part 3 of the StyloBot Release Series is up.

    mostlylucid.net/blog/stylobot-

    This one is less about bots and more about the reality of long-running .NET based systems: everything that learns from traffic eventually accumulates.

    Came from one of my periodic reliability reviews where StyloBot’s vector layer had drifted to 13GB on the .NET Large Object Heap due to the wrong abstraction (in-process HNSW behaving like an unbounded cache).

    The interesting part wasn’t the fix. It was recognising that the architecture itself was wrong for the runtime pattern.

    Covers:

    how I periodically review long-running services

    using dotnet-counters, dotMemory and dotTrace to find growth

    why “just add a cap” is often the wrong answer

    replacing unbounded ANN structures with bounded hot caches + compacted persistence

    taking the vector layer from 13GB LOH to <6MB

    The broader point applies to any system that “remembers”:

    bot detection, fraud scoring, recommendations, anomaly detection, RAG pipelines, adaptive systems.

    Fix the shape, not the symptom.

    #dotnet #aspnetcore #performance #architecture #ai #rag #observability

  7. Part 3 of the StyloBot Release Series is up.

    mostlylucid.net/blog/stylobot-

    This one is less about bots and more about the reality of long-running .NET based systems: everything that learns from traffic eventually accumulates.

    Came from one of my periodic reliability reviews where StyloBot’s vector layer had drifted to 13GB on the .NET Large Object Heap due to the wrong abstraction (in-process HNSW behaving like an unbounded cache).

    The interesting part wasn’t the fix. It was recognising that the architecture itself was wrong for the runtime pattern.

    Covers:

    how I periodically review long-running services

    using dotnet-counters, dotMemory and dotTrace to find growth

    why “just add a cap” is often the wrong answer

    replacing unbounded ANN structures with bounded hot caches + compacted persistence

    taking the vector layer from 13GB LOH to <6MB

    The broader point applies to any system that “remembers”:

    bot detection, fraud scoring, recommendations, anomaly detection, RAG pipelines, adaptive systems.

    Fix the shape, not the symptom.

  8. Part 3 of the StyloBot Release Series is up.

    mostlylucid.net/blog/stylobot-

    This one is less about bots and more about the reality of long-running .NET based systems: everything that learns from traffic eventually accumulates.

    Came from one of my periodic reliability reviews where StyloBot’s vector layer had drifted to 13GB on the .NET Large Object Heap due to the wrong abstraction (in-process HNSW behaving like an unbounded cache).

    The interesting part wasn’t the fix. It was recognising that the architecture itself was wrong for the runtime pattern.

    Covers:

    how I periodically review long-running services

    using dotnet-counters, dotMemory and dotTrace to find growth

    why “just add a cap” is often the wrong answer

    replacing unbounded ANN structures with bounded hot caches + compacted persistence

    taking the vector layer from 13GB LOH to <6MB

    The broader point applies to any system that “remembers”:

    bot detection, fraud scoring, recommendations, anomaly detection, RAG pipelines, adaptive systems.

    Fix the shape, not the symptom.

    #dotnet #aspnetcore #performance #architecture #ai #rag #observability

  9. Part 3 of the StyloBot Release Series is up.

    mostlylucid.net/blog/stylobot-

    This one is less about bots and more about the reality of long-running .NET based systems: everything that learns from traffic eventually accumulates.

    Came from one of my periodic reliability reviews where StyloBot’s vector layer had drifted to 13GB on the .NET Large Object Heap due to the wrong abstraction (in-process HNSW behaving like an unbounded cache).

    The interesting part wasn’t the fix. It was recognising that the architecture itself was wrong for the runtime pattern.

    Covers:

    how I periodically review long-running services

    using dotnet-counters, dotMemory and dotTrace to find growth

    why “just add a cap” is often the wrong answer

    replacing unbounded ANN structures with bounded hot caches + compacted persistence

    taking the vector layer from 13GB LOH to <6MB

    The broader point applies to any system that “remembers”:

    bot detection, fraud scoring, recommendations, anomaly detection, RAG pipelines, adaptive systems.

    Fix the shape, not the symptom.

    #dotnet #aspnetcore #performance #architecture #ai #rag #observability

  10. Unit testing user interfaces makes some people uncomfortable.

    Read more here:
    bgh.st/3br4dp

    #blazor #aspnet #dotnet #testing

  11. #Microsoft issues emergency update for #macOS and #Linux ASP.NET threat

    Microsoft released an emergency patch for its ASP.NET Core to fix a high-severity #vulnerability that allows unauthenticated attackers to gain SYSTEM privileges on devices that use the Web development framework to run Linux or macOS apps.

    The software maker said Tuesday evening that the vulnerability, tracked as CVE-2026-40372
    #ASPNet #security

    arstechnica.com/security/2026/

  12. Has your company recently asked you to implement #SAML 2.0? Worried about the prospect of implementing the 20-year-old protocol?

    Come check out how to implement SAML 2.0 into Duende IdentityServer. #dotnet #saml #security #aspnetcore

    🙏 boosts appreciated #livestream

    youtube.com/watch?v=o_tGJ9KHdns