<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Http on Duc Truong</title>
    <link>https://ductruong.com/en/tags/http/</link>
    <description>Recent content in Http on Duc Truong</description>
    <generator>Hugo -- 0.144.2</generator>
    <language>en</language>
    <lastBuildDate>Wed, 15 May 2024 16:30:10 +0700</lastBuildDate>
    <atom:link href="https://ductruong.com/en/tags/http/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Designing a High-Load File Upload System with the Tus Protocol</title>
      <link>https://ductruong.com/en/blog/2024/05/designing-a-high-load-file-upload-system-with-the-tus-protocol/</link>
      <pubDate>Wed, 15 May 2024 16:30:10 +0700</pubDate>
      <guid>https://ductruong.com/en/blog/2024/05/designing-a-high-load-file-upload-system-with-the-tus-protocol/</guid>
      <description>&lt;p&gt;Hello everyone, uploading data to the internet happens every day, from uploading photos to Facebook, videos to YouTube, TikTok, or files to
Google Drive, etc. Files can range from small to very large sizes, but network environments have never been stable 😅, with jitter, lag, or
sudden disconnections 🤯. Have you ever wondered how to deploy a system capable of resuming an upload even if the connection is lost midway?&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
