<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Kavathiyakhushali on Medium]]></title>
        <description><![CDATA[Stories by Kavathiyakhushali on Medium]]></description>
        <link>https://medium.com/@kavathiyakhushali?source=rss-ee297bde666f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*84nTYaGV9y4JgbbU</url>
            <title>Stories by Kavathiyakhushali on Medium</title>
            <link>https://medium.com/@kavathiyakhushali?source=rss-ee297bde666f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 18:36:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kavathiyakhushali/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Your .NET Application Works. But Is It Actually Production-Ready?]]></title>
            <link>https://medium.com/codetodeploy/your-net-application-works-but-is-it-actually-production-ready-39b5e033397d?source=rss-ee297bde666f------2</link>
            <guid isPermaLink="false">https://medium.com/p/39b5e033397d</guid>
            <category><![CDATA[optimization]]></category>
            <category><![CDATA[backend]]></category>
            <category><![CDATA[dotnet]]></category>
            <category><![CDATA[deployment]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Kavathiyakhushali]]></dc:creator>
            <pubDate>Tue, 17 Nov 2026 09:38:33 GMT</pubDate>
            <atom:updated>2026-11-17T09:44:58.041Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hZZyUIbVjs8vHJXwWKGX7w.png" /></figure><h3>7 things I check before calling an ASP.NET Core application production-ready</h3><p>An ASP.NET Core application can work perfectly on your machine and still be completely unprepared for production.</p><blockquote><em>💥 </em><strong><em>Master AI &amp; Tech Skills </em></strong><br> 🔥 Up to 5<strong>0% OFF</strong> — Limited-Time Offer<br><a href="https://trk.udemy.com/zz4NBO"><em>👉 </em><strong><em>Enroll Now &amp; Start Learning</em></strong></a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ITogvtC6mF2BUF35Qsd9pg.png" /></figure><p>The API returns 200 OK.</p><p>The database connection works.</p><p>The UI looks good.</p><p>Your tests are passing.</p><p>You deploy it.</p><p>And then reality starts.</p><p>Requests become slow. A third-party API times out. Database connections pile up. Logs don’t tell you what happened. One unexpected exception exposes information that should never have reached the client.</p><p>This is the difference between <strong>“the application works”</strong> and <strong>“the application is ready for production.”</strong></p><p>Production readiness isn’t one feature or one checklist. It’s about how the application behaves when traffic increases, dependencies fail, users make unexpected requests, and something inevitably goes wrong.</p><p>Here are seven areas I would check before calling an ASP.NET Core application production-ready.</p><h3>1. Can the application handle real traffic?</h3><p>The first question isn’t:</p><blockquote><em>“Does the API return the correct response?”</em></blockquote><p>It’s:</p><blockquote><em>“What happens when hundreds or thousands of requests arrive at the same time?”</em></blockquote><p>A common mistake is writing code that works perfectly during development but blocks threads under load.</p><p>For example:</p><pre>var result = httpClient.GetAsync(url).Result;</pre><p>It looks simple, but blocking asynchronous operations can contribute to Thread Pool starvation and degraded response times in ASP.NET Core.</p><p>Prefer asynchronous execution:</p><pre>var result = await httpClient.GetAsync(url);</pre><p>The same principle applies to database access and other I/O operations.</p><p>Microsoft’s ASP.NET Core guidance specifically recommends avoiding blocking calls and using asynchronous APIs for data access, I/O, and long-running operations.</p><p>But async/await isn’t the whole performance story.</p><p>You also need to look at:</p><ul><li>Database queries</li><li>External API calls</li><li>Serialization</li><li>Large response payloads</li><li>Memory allocations</li><li>Middleware</li><li>Caching</li><li>Network round trips</li></ul><p>The important question is not whether one endpoint is fast on your laptop.</p><p>It’s whether your application stays predictable when the workload changes.</p><h3>2. Is your database doing unnecessary work?</h3><p>A surprising amount of application performance comes down to how efficiently you access data.</p><p>Consider:</p><pre>var users = await db.Users.ToListAsync();</pre><p>If your table contains 500,000 records and your endpoint needs only five users, the code is technically correct.</p><p>It is also doing far more work than necessary.</p><p>A better query might be:</p><pre>var users = await db.Users<br>    .Where(x =&gt; x.IsActive)<br>    .Select(x =&gt; new UserDto<br>    {<br>        Id = x.Id,<br>        Name = x.Name<br>    })<br>    .Take(5)<br>    .ToListAsync();</pre><p>Now the database can return only the data the endpoint actually needs.</p><p>This becomes even more important as applications grow.</p><p>Look for:</p><ul><li>ToList() before filtering</li><li>N+1 queries</li><li>Missing pagination</li><li>Selecting entire entities unnecessarily</li><li>Unnecessary Include() calls</li><li>Queries without appropriate indexes</li><li>Multiple round trips to the database</li><li>Tracking queries where tracking isn’t required</li></ul><p>Microsoft recommends retrieving only the data needed for the request, minimizing network round trips, and using no-tracking queries for read-only EF Core scenarios where appropriate.</p><p>A production application should make the database work <strong>with</strong> the application, not against it.</p><h3>3. What happens when something fails?</h3><p>This is one of the biggest differences between development and production.</p><p>In development, you want detailed exceptions.</p><p>In production, your users don’t need to see your stack trace, internal class names, connection details, or other implementation information.</p><p>For example, this is something you never want to expose publicly:</p><pre>System.InvalidOperationException:<br>Connection failed to SQL Server...<br>at MyApplication.Services.UserService...<br>at MyApplication.Controllers.UsersController...</pre><p>ASP.NET Core provides the Developer Exception Page for development, but Microsoft explicitly warns against exposing detailed exception information in production.</p><p>Instead, configure production error handling.</p><p>For example:</p><pre>builder.Services.AddProblemDetails();<br>var app = builder.Build();<br>app.UseExceptionHandler();<br>app.MapControllers();</pre><p>The client can receive a safe error response while the application records the actual exception internally.</p><p>This creates an important separation:</p><p><strong>User gets:</strong><br>A safe, useful error.</p><p><strong>Developer gets:</strong><br>The information required to investigate the failure.</p><p>That’s what production error handling should look like.</p><h3>4. Can you actually diagnose a production problem?</h3><p>Imagine someone reports:</p><blockquote><em>“The API was slow at 2:30 PM.”</em></blockquote><p>What can you tell them?</p><p>If your answer is:</p><blockquote><em>“I don’t know. Let me check the logs.”</em></blockquote><p>that’s not enough.</p><p>Good production logging should help you answer questions such as:</p><ul><li>Which request failed?</li><li>Which user or operation was involved?</li><li>Which dependency was slow?</li><li>How long did the database call take?</li><li>Did an external API fail?</li><li>What exception occurred?</li><li>What happened immediately before the failure?</li></ul><p>A request or correlation ID can make a huge difference.</p><p>For example:</p><pre>RequestId: 7f2a91<br>Endpoint: /api/orders/123<br>UserId: 451<br>Database: 820ms<br>Payment API: 2100ms<br>Status: 500</pre><p>Now you have something to investigate.</p><p>But logging everything isn’t the answer either.</p><p>ASP.NET Core’s HTTP logging can record request and response information, but Microsoft notes that logging request and response bodies can have a performance impact.</p><p>Production logging needs to be <strong>useful, structured, and intentional</strong>.</p><p>Don’t log secrets.</p><p>Don’t log passwords.</p><p>Don’t dump huge request bodies into every log.</p><p>Don’t make developers search through thousands of meaningless messages to find one failure.</p><h3>5. What happens when a dependency goes down?</h3><p>Your application probably doesn’t live alone.</p><p>It might depend on:</p><ul><li>SQL Server</li><li>PostgreSQL</li><li>Redis</li><li>Payment services</li><li>Email providers</li><li>Storage services</li><li>Authentication providers</li><li>Internal APIs</li><li>External APIs</li></ul><p>Now imagine your payment provider takes 10 seconds to respond.</p><p>If your application simply waits, every request can become slower.</p><p>Eventually, users experience:</p><pre>Request<br>   ↓<br>Payment API<br>   ↓<br>Waiting...<br>   ↓<br>Waiting...<br>   ↓<br>Timeout</pre><p>And if enough requests do this simultaneously, the problem can spread through your application.</p><p>Production systems need explicit policies around dependency failures.</p><p>Depending on the scenario, that can include:</p><ul><li>Timeouts</li><li>Retries</li><li>Circuit breakers</li><li>Fallbacks</li><li>Cancellation</li><li>Idempotency</li><li>Bulkheads</li><li>Queue-based processing</li></ul><p>But there’s an important warning:</p><p><strong>Don’t blindly add retries everywhere.</strong></p><p>Retrying a failed operation can make things worse if the dependency is already overloaded.</p><p>For example:</p><pre>100 requests fail<br>      ↓<br>100 retries<br>      ↓<br>dependency receives another 100 requests<br>      ↓<br>dependency becomes even less healthy</pre><p>Resilience should be designed around the failure mode, not added as a collection of middleware packages.</p><h3>6. Can users abuse your API?</h3><p>Your API might work perfectly for normal users.</p><p>But what happens if one client sends:</p><pre>1 request<br>10 requests<br>100 requests<br>10,000 requests</pre><p>A public API shouldn’t assume every caller behaves reasonably.</p><p>Rate limiting can protect resources and help prevent a single client from consuming an unfair amount of capacity.</p><p>ASP.NET Core provides built-in rate-limiting middleware through Microsoft.AspNetCore.RateLimiting, allowing policies to be applied to endpoints. Microsoft also recommends testing and reviewing rate-limiting configurations before deployment.</p><p>For example:</p><pre>builder.Services.AddRateLimiter(options =&gt;<br>{<br>    options.AddFixedWindowLimiter(&quot;api&quot;, limiterOptions =&gt;<br>    {<br>        limiterOptions.PermitLimit = 100;<br>        limiterOptions.Window = TimeSpan.FromMinutes(1);<br>    });<br>});</pre><p>Then apply the policy to appropriate endpoints.</p><p>The exact limits depend on your application.</p><p>A login endpoint might need very different limits from a public product-search endpoint.</p><p>The important idea is:</p><blockquote><strong><em>Production systems should control how much work one client can force the system to perform.</em></strong></blockquote><h3>7. What happens to long-running operations?</h3><p>One of the easiest mistakes is making an HTTP request do too much work.</p><p>Imagine an endpoint that:</p><ol><li>Uploads a large file</li><li>Parses the file</li><li>Calls an external API</li><li>Generates embeddings</li><li>Processes thousands of records</li><li>Updates a database</li><li>Returns the final result</li></ol><p>The user might be waiting for 30 seconds.</p><p>Or 2 minutes.</p><p>Or longer.</p><p>That’s a sign that the work may not belong entirely inside the HTTP request.</p><p>A better architecture might look like:</p><pre>Client<br>  ↓<br>POST /process<br>  ↓<br>Create Job<br>  ↓<br>Queue<br>  ↓<br>Background Worker<br>  ↓<br>Long-running processing<br>  ↓<br>Store result<br>  ↓<br>Client checks status</pre><p>ASP.NET Core guidance recommends moving long-running work outside ordinary HTTP request processing, using background services or out-of-process solutions where appropriate.</p><p>The HTTP request should often be responsible for <strong>starting the work</strong>, not doing every piece of it.</p><h3>The production-readiness test</h3><p>Before deploying an ASP.NET Core application, I like to think through questions such as:</p><h3>Performance</h3><ul><li>What happens when traffic increases?</li><li>Are database calls efficient?</li><li>Are there unnecessary network calls?</li><li>Are large objects being allocated repeatedly?</li></ul><h3>Reliability</h3><ul><li>What happens when SQL Server is unavailable?</li><li>What happens when an external API times out?</li><li>Are retries controlled?</li><li>Can operations be safely repeated?</li></ul><h3>Security</h3><ul><li>Are secrets outside source control?</li><li>Is sensitive information excluded from logs?</li><li>Are production errors hiding internal details?</li><li>Are public endpoints protected against abuse?</li></ul><h3>Observability</h3><ul><li>Can I identify a failed request?</li><li>Can I understand where time was spent?</li><li>Do I have useful logs and metrics?</li><li>Can I distinguish application failures from dependency failures?</li></ul><h3>Operations</h3><ul><li>Is there a health check?</li><li>Can the application be deployed safely?</li><li>Can failed background jobs be detected?</li><li>Can the application be rolled back?</li></ul><p>These questions are much more important than simply asking:</p><blockquote><em>“Does the application work?”</em></blockquote><h3>Working is not the same as being production-ready</h3><p>This is probably the biggest lesson.</p><p>A developer can write an API that works.</p><p>A production-ready application needs to do more than work.</p><p>It needs to:</p><p><strong>Work under load.</strong></p><p><strong>Fail safely.</strong></p><p><strong>Recover from dependency failures.</strong></p><p><strong>Protect itself from abuse.</strong></p><p><strong>Provide enough information to diagnose problems.</strong></p><p><strong>Avoid unnecessary work.</strong></p><p><strong>Handle long-running operations appropriately.</strong></p><p>That’s why production readiness isn’t something you add the day before deployment.</p><p>It should influence the architecture from the beginning.</p><h3>A simple mindset shift</h3><p>Instead of asking:</p><blockquote><strong><em>“Does this feature work?”</em></strong></blockquote><p>start asking:</p><blockquote><strong><em>“What happens when this feature doesn’t work?”</em></strong></blockquote><p>Instead of:</p><blockquote><strong><em>“Is this API fast?”</em></strong></blockquote><p>ask:</p><blockquote><strong><em>“What happens when 1,000 clients call it at the same time?”</em></strong></blockquote><p>Instead of:</p><blockquote><strong><em>“Did the deployment succeed?”</em></strong></blockquote><p>ask:</p><blockquote><strong><em>“How will I know if the application starts failing after deployment?”</em></strong></blockquote><p>Those questions lead to better production software.</p><p>Your code doesn’t become production-ready because it passed your local tests.</p><p>It becomes production-ready when you’ve thought about what happens <strong>after everything stops going according to plan.</strong></p><h3>Final thought</h3><p>Every developer eventually learns this lesson:</p><p><strong>The happy path is the easy part.</strong></p><p>Production is where the unhappy paths matter.</p><p>And that’s where good engineering starts.</p><p>What is the <strong>first thing you check before deploying a .NET application to production — performance, security, logging, database, or failure handling?</strong></p><h3>Thank you for being a part of the community</h3><p><em>Before you go:</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d9QTaaaxboQP_gKSLedW_w.png" /></figure><p>👉 Be sure to <strong>clap</strong> and <strong>follow</strong> the writer ️👏<strong>️️</strong></p><p>👉 Follow us: <a href="https://medium.com/codetodeploy"><strong>Medium</strong></a></p><p><strong>Disclosure:</strong> This post includes affiliate and partnership links.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=39b5e033397d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/codetodeploy/your-net-application-works-but-is-it-actually-production-ready-39b5e033397d">Your .NET Application Works. But Is It Actually Production-Ready?</a> was originally published in <a href="https://medium.com/codetodeploy">CodeToDeploy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Explored Anthropic Academy. Here Are the Claude Courses .NET Developers Should Know About in 2026]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://blog.gopenai.com/i-explored-anthropic-academy-here-are-the-claude-courses-net-developers-should-know-about-in-2026-d3811e92ec0f?source=rss-ee297bde666f------2"><img src="https://cdn-images-1.medium.com/max/1376/1*__G0BRBlXnaws5bDfYzXPA.png" width="1376"></a></p><p class="medium-feed-snippet">Subtitle: Exploring Claude&#x2019;s developer learning resources, the four professional certification paths, and what .NET</p><p class="medium-feed-link"><a href="https://blog.gopenai.com/i-explored-anthropic-academy-here-are-the-claude-courses-net-developers-should-know-about-in-2026-d3811e92ec0f?source=rss-ee297bde666f------2">Continue reading on GoPenAI »</a></p></div>]]></description>
            <link>https://blog.gopenai.com/i-explored-anthropic-academy-here-are-the-claude-courses-net-developers-should-know-about-in-2026-d3811e92ec0f?source=rss-ee297bde666f------2</link>
            <guid isPermaLink="false">https://medium.com/p/d3811e92ec0f</guid>
            <category><![CDATA[claude-ai]]></category>
            <category><![CDATA[anthropic-claude]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[dotnet]]></category>
            <dc:creator><![CDATA[Kavathiyakhushali]]></dc:creator>
            <pubDate>Mon, 02 Nov 2026 06:06:44 GMT</pubDate>
            <atom:updated>2026-11-04T02:56:50.506Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[My AI Feature Worked. Then I Looked at the Cost.]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://towardsdev.com/my-ai-feature-worked-then-i-looked-at-the-cost-018361bafbe3?source=rss-ee297bde666f------2"><img src="https://cdn-images-1.medium.com/max/1376/1*VpLUkHwplfSdsEmN2RSmXA.png" width="1376"></a></p><p class="medium-feed-snippet">Subtitle: An AI feature can work perfectly and still be too expensive to scale. Here are the hidden costs .NET developers should measure&#x2026;</p><p class="medium-feed-link"><a href="https://towardsdev.com/my-ai-feature-worked-then-i-looked-at-the-cost-018361bafbe3?source=rss-ee297bde666f------2">Continue reading on Towards Dev »</a></p></div>]]></description>
            <link>https://towardsdev.com/my-ai-feature-worked-then-i-looked-at-the-cost-018361bafbe3?source=rss-ee297bde666f------2</link>
            <guid isPermaLink="false">https://medium.com/p/018361bafbe3</guid>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[llm]]></category>
            <category><![CDATA[dotnet]]></category>
            <dc:creator><![CDATA[Kavathiyakhushali]]></dc:creator>
            <pubDate>Fri, 23 Oct 2026 13:21:32 GMT</pubDate>
            <atom:updated>2026-11-04T16:01:26.422Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[AI Agents Can Pass Your Demo and Still Fail in Production]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://blog.gopenai.com/ai-agents-can-pass-your-demo-and-still-fail-in-production-8a275cd17b6c?source=rss-ee297bde666f------2"><img src="https://cdn-images-1.medium.com/max/1536/1*vYTUfgK_Uqq0m3wBAMv94Q.jpeg" width="1536"></a></p><p class="medium-feed-snippet">Your .NET AI agent works perfectly with sample prompts. Here&#x2019;s why testing its real behavior requires more than checking the final answer.</p><p class="medium-feed-link"><a href="https://blog.gopenai.com/ai-agents-can-pass-your-demo-and-still-fail-in-production-8a275cd17b6c?source=rss-ee297bde666f------2">Continue reading on GoPenAI »</a></p></div>]]></description>
            <link>https://blog.gopenai.com/ai-agents-can-pass-your-demo-and-still-fail-in-production-8a275cd17b6c?source=rss-ee297bde666f------2</link>
            <guid isPermaLink="false">https://medium.com/p/8a275cd17b6c</guid>
            <category><![CDATA[generative-ai-tools]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[dotnet]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Kavathiyakhushali]]></dc:creator>
            <pubDate>Thu, 15 Oct 2026 04:53:06 GMT</pubDate>
            <atom:updated>2026-10-15T11:35:05.909Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[I Built a Text-to-SQL Agent in .NET. Here’s What Broke.]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://towardsdev.com/i-built-a-text-to-sql-agent-in-net-heres-what-broke-63cdf880349d?source=rss-ee297bde666f------2"><img src="https://cdn-images-1.medium.com/max/1376/1*1rbi4leM5AqF_k2YcIViOA.png" width="1376"></a></p><p class="medium-feed-snippet">Turning natural language into SQL sounds simple. In practice, schema context, hallucinations, validation, permissions, and follow-up&#x2026;</p><p class="medium-feed-link"><a href="https://towardsdev.com/i-built-a-text-to-sql-agent-in-net-heres-what-broke-63cdf880349d?source=rss-ee297bde666f------2">Continue reading on Towards Dev »</a></p></div>]]></description>
            <link>https://towardsdev.com/i-built-a-text-to-sql-agent-in-net-heres-what-broke-63cdf880349d?source=rss-ee297bde666f------2</link>
            <guid isPermaLink="false">https://medium.com/p/63cdf880349d</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[dotnet]]></category>
            <category><![CDATA[text-to-sql]]></category>
            <category><![CDATA[sql-server]]></category>
            <dc:creator><![CDATA[Kavathiyakhushali]]></dc:creator>
            <pubDate>Mon, 05 Oct 2026 05:06:20 GMT</pubDate>
            <atom:updated>2026-10-06T12:58:27.328Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Your AI Agent Has Tools. Now Secure Them.]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://blog.gopenai.com/your-ai-agent-has-tools-now-secure-them-f61110e9c6e1?source=rss-ee297bde666f------2"><img src="https://cdn-images-1.medium.com/max/1376/1*wq5W_jnVGQyrKWeB5HxQbg.png" width="1376"></a></p><p class="medium-feed-snippet">Giving an AI agent access to tools changes everything. Here&#x2019;s what I learned about permissions, validation, human approval, and safe tool&#x2026;</p><p class="medium-feed-link"><a href="https://blog.gopenai.com/your-ai-agent-has-tools-now-secure-them-f61110e9c6e1?source=rss-ee297bde666f------2">Continue reading on GoPenAI »</a></p></div>]]></description>
            <link>https://blog.gopenai.com/your-ai-agent-has-tools-now-secure-them-f61110e9c6e1?source=rss-ee297bde666f------2</link>
            <guid isPermaLink="false">https://medium.com/p/f61110e9c6e1</guid>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[mcp-server]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Kavathiyakhushali]]></dc:creator>
            <pubDate>Tue, 29 Sep 2026 08:13:51 GMT</pubDate>
            <atom:updated>2026-09-29T12:53:44.975Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[I Added Redis Memory to My AI Agent. Here’s What I Got Wrong]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://blog.gopenai.com/i-added-redis-memory-to-my-ai-agent-heres-what-i-got-wrong-e069edce5c8f?source=rss-ee297bde666f------2"><img src="https://cdn-images-1.medium.com/max/1672/1*E6tKQSBmK6XgfR_blqO_yw.png" width="1672"></a></p><p class="medium-feed-snippet">I thought giving an AI agent memory was simple. Store the conversation in Redis, send it back to the model, and you&#x2019;re done. I was wrong.</p><p class="medium-feed-link"><a href="https://blog.gopenai.com/i-added-redis-memory-to-my-ai-agent-heres-what-i-got-wrong-e069edce5c8f?source=rss-ee297bde666f------2">Continue reading on GoPenAI »</a></p></div>]]></description>
            <link>https://blog.gopenai.com/i-added-redis-memory-to-my-ai-agent-heres-what-i-got-wrong-e069edce5c8f?source=rss-ee297bde666f------2</link>
            <guid isPermaLink="false">https://medium.com/p/e069edce5c8f</guid>
            <category><![CDATA[llm]]></category>
            <category><![CDATA[redis]]></category>
            <category><![CDATA[dotnet]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[ai-engineering]]></category>
            <dc:creator><![CDATA[Kavathiyakhushali]]></dc:creator>
            <pubDate>Thu, 24 Sep 2026 10:32:52 GMT</pubDate>
            <atom:updated>2026-09-24T12:15:23.914Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Why Your AI Application Is Slow — And the Model Might Not Be the Problem]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://blog.gopenai.com/why-your-ai-application-is-slow-and-the-model-might-not-be-the-problem-03d893a258f7?source=rss-ee297bde666f------2"><img src="https://cdn-images-1.medium.com/max/1376/1*swd3xVnVg-EjFJIqMCA2sA.png" width="1376"></a></p><p class="medium-feed-snippet">You switched to a faster model. Your AI app is still slow. Here&#x2019;s why.</p><p class="medium-feed-link"><a href="https://blog.gopenai.com/why-your-ai-application-is-slow-and-the-model-might-not-be-the-problem-03d893a258f7?source=rss-ee297bde666f------2">Continue reading on GoPenAI »</a></p></div>]]></description>
            <link>https://blog.gopenai.com/why-your-ai-application-is-slow-and-the-model-might-not-be-the-problem-03d893a258f7?source=rss-ee297bde666f------2</link>
            <guid isPermaLink="false">https://medium.com/p/03d893a258f7</guid>
            <category><![CDATA[ai-engineering]]></category>
            <category><![CDATA[dotnet]]></category>
            <category><![CDATA[llm]]></category>
            <category><![CDATA[rags]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Kavathiyakhushali]]></dc:creator>
            <pubDate>Fri, 18 Sep 2026 05:16:38 GMT</pubDate>
            <atom:updated>2026-09-24T12:07:22.747Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[MCP Just Changed. Here’s What .NET Developers Actually Need to Know]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://towardsdev.com/mcp-just-changed-heres-what-net-developers-actually-need-to-know-50c76f0f7a9d?source=rss-ee297bde666f------2"><img src="https://cdn-images-1.medium.com/max/1376/1*kCvhxPzlU4tJEcirgCyKIw.png" width="1376"></a></p><p class="medium-feed-snippet">How MCP C# SDK 2.0 changes the way you build and scale AI tools with ASP.NET Core</p><p class="medium-feed-link"><a href="https://towardsdev.com/mcp-just-changed-heres-what-net-developers-actually-need-to-know-50c76f0f7a9d?source=rss-ee297bde666f------2">Continue reading on Towards Dev »</a></p></div>]]></description>
            <link>https://towardsdev.com/mcp-just-changed-heres-what-net-developers-actually-need-to-know-50c76f0f7a9d?source=rss-ee297bde666f------2</link>
            <guid isPermaLink="false">https://medium.com/p/50c76f0f7a9d</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[aspnetcore]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[mcp-server]]></category>
            <category><![CDATA[dotnet]]></category>
            <dc:creator><![CDATA[Kavathiyakhushali]]></dc:creator>
            <pubDate>Fri, 11 Sep 2026 05:43:48 GMT</pubDate>
            <atom:updated>2026-09-11T06:13:33.256Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Your AI Doesn’t Need One Model Anymore]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://blog.gopenai.com/your-ai-doesnt-need-one-model-anymore-88bfda62ad43?source=rss-ee297bde666f------2"><img src="https://cdn-images-1.medium.com/max/1376/1*seObHLzC8WqXyWciWJJiwQ.png" width="1376"></a></p><p class="medium-feed-snippet">How .NET applications can route, switch, and fail over between AI models</p><p class="medium-feed-link"><a href="https://blog.gopenai.com/your-ai-doesnt-need-one-model-anymore-88bfda62ad43?source=rss-ee297bde666f------2">Continue reading on GoPenAI »</a></p></div>]]></description>
            <link>https://blog.gopenai.com/your-ai-doesnt-need-one-model-anymore-88bfda62ad43?source=rss-ee297bde666f------2</link>
            <guid isPermaLink="false">https://medium.com/p/88bfda62ad43</guid>
            <category><![CDATA[llm]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[ai-engineering]]></category>
            <category><![CDATA[dotnet]]></category>
            <dc:creator><![CDATA[Kavathiyakhushali]]></dc:creator>
            <pubDate>Sun, 06 Sep 2026 21:11:01 GMT</pubDate>
            <atom:updated>2026-09-06T21:11:01.433Z</atom:updated>
        </item>
    </channel>
</rss>