DiscDot provides insights into distributed systems, cloud computing, and scalable architectures, offering articles and best practices for designing and implementing resilient and scalable distributed systems. By exploring DiscDot's curated content, developers can learn about distributed data storage, fault-tolerance mechanisms, and distributed computing frameworks for building highly available and performant applications. Whether you're architecting microservices, deploying containerized workloads, or managing distributed databases, DiscDot offers  insights and practical guidance to help you tackle the challenges of building distributed systems.

Discover .NET

Improving performance and memory use while accessing APIs using HTTPClient in dotnet. In this article, let's learn about how to use Stream while reading data from API Using Stream while sending data to API. Let's explore how we can implement this improvement using in place of.NET.

Improving performance and memory use while accessing APIs using HTTPClient in dotnet

<p>Nice article and the use of stream is for sure the way to go. I do lack however the real optimizations that the title implies in regards to the Http Client. For example in this post by Josef Ottosson a lot more details are presented with also a look on other pitfalls:
<a href="https://josef.codes/you-are-probably-still-using-httpclient-wrong-and-it-is-destabilizing-your-software" target="_blank" rel="noopener nofollow">https://josef.codes/you-are-probably-still-using-httpclient-wrong-and-it-is-destabilizing-your-software</a></p>


<p>Waiting for the API response is already going to be extremely slow relative to local code, this is overoptimization</p>
