<div id="readability-page-1" class="page"><div><p><img src="https://github.com/joosing/fireball/assets/34666301/d4665a3f-84de-4197-8007-4e7d21c663e3"></p>
<p>🚩 <a href="https://github.com/joosing/fireball">GitHub Link</a></p>
<h2 id="overview">Overview</h2>
<p>The Fireball project provides a small, independent service for quickly transferring large files. No matter what language or framework you use, you can quickly exchange files with a remote location via a simple HTTP request.</p>
<pre><code>Method: POST
URL: http://localhost:58080/api/upload
Content-Type: application/json

{
  "source": {
    "file": "source.dat"
  },
  "destination": {
    "ip": "127.0.0.1",
    "port": 50711,
    "file": "destination.dat"
  }
}</code></pre>
<h2 id="problem">Problem</h2>
<p>Anyone can easily write code to exchange files over a network. However, depending on which tool you use and how well you optimize it, there is a big difference in processing performance.</p>
<h3 id="many-methods-difference-performance">Many Methods, Difference Performance</h3>
<p>I tested sending a 1GB file over a loopback network using several representative methods (including Fireball). After 50 iterations of the test, the average was measured, and a typical performance home laptop (Acer Swift 5 Notebook) was used for the test. The time for one measurement includes the time from reading the file, sending it to the network, saving the received file again, and until the response is complete. In the test results below, you can see that even though we're processing the same file under the same conditions, which method we use makes a big difference in performance.</p>
<p><img src="https://velog.velcdn.com/images/joosing/post/3cab2576-ab0e-4dc2-b81a-e1b5b014fa08/image.png"></p>
<h2 id="goal">Goal</h2>
<p>In above tests, Fireball is not the best performing method, the best performance is achieved by bringing up a Windows FTP server and using the .NET API. The Fireball project will continue to push for better performance in the future. In addition, we want to provide the following core values together.</p>
<ul>
<li>Small, independent service focused on file transfer.</li>
<li>Service that can be used in any language, any framework, any platform.</li>
<li>Simple programming API.</li>
<li>Single application that integrates the server and the client.</li>
</ul>
<h2 id="build">Build</h2>
<p>Fireball is a Spring Boot project and uses Maven as its build tool. You can now clone the project, navigate to the root path (where the mvnw file exists), and build the project using the maven wrapper (mvnw). The build result file exists in ./target/fireball-0.0.1.final.jar.</p>
<pre><code>&gt; git clone https://github.com/joosing/fireball.git
&gt; cd fireball
&gt; chmod 744 mvnw
&gt; ./mvnw clean package -DskipTests</code></pre>
<h2 id="install">Install</h2>
<p>To use Fireball to exchange files between different network hosts, the Fireball service must be installed and running on both hosts.</p>
<ul>
<li>First, make sure you have the Java 17 version installed.</li>
</ul>
<pre><code>&gt; java --version </code></pre>
<ul>
<li>Copy the built JAR file to the desired path.</li>
</ul>
<pre><code>&gt; cp ./target/fireball-0.0.1.final.jar /app/fireball/fireball-0.0.1.final.jar</code></pre>
<h2 id="run">Run</h2>
<p>Run the Fireball with the following settings</p>
<ul>
<li>file.client.root : Specify the path to the file root on the client (required)</li>
<li>file.server.root : Specify the path to the file root on the server (required)</li>
<li>server.port : Specify the API server port (Optional, uses port 58080 if not specified)</li>
<li>file.server.port : Specify the file server port (Optional, uses port 50711 if not specified)</li>
</ul>
<pre><code>&gt; java -Dfile.server.root="/app/files" -Dfile.client.root="/app/files" -jar fireball-0.0.1.final.jar</code></pre>
<h2 id="usage">Usage</h2>
<p>Fireball provides two REST APIs for file upload and download. Here is an example of a system configured using Fireball. In this example, the user service is installed on host A (192.168.10.10), and the Fireball service is installed on hosts B (192.168.100.10) and C (192.168.100.11). User sends a file exchange request to Host B. In this case, the Fireball service on Host B will be in the file client role and Fireball on Host C will be in the file server role. The following sections describe example requests that perform file uploads and downloads between Hosts B and C within this configuration.</p>
<p><img src="https://github.com/joosing/fireball/assets/34666301/fc36d798-fcd8-4b9f-b87c-34c7b06536c2"></p>
<h3 id="a-upload">A. Upload</h3>
<p>You can upload a file from Host B to Host C with a simple HTTP request like the following. The example uploads the source.dat file on host B to the /parent/destination.dat file on host C. Each file path is relative to the set root path. If the /parent directory does not exist, it will automatically create it and if the destination.dat file already exists, it will overwrite the existing file and create a new one.</p>
<pre><code>Method: POST
URL: http://192.168.100.10:58080/api/upload
Content-Type: application/json

{
  "source": {
    "file": "source.dat"
  },
  "destination": {
    "ip": "192.168.100.11",
    "port": 50711,
    "file": "/parent/destination.dat"
  }
}</code></pre>
<h3 id="b-download">B. Download</h3>
<p>You can download files from host C to B with a simple HTTP request like the following. The example downloads the source.dat file on host C to the /parent/destination.dat file on host B. Each file path is relative to the set root path. If the /parent directory does not exist, it will automatically create it, and if the destination.dat file already exists, it will overwrite the existing file and create a new one.</p>
<pre><code>Method: POST
URL: http://192.168.100.10:58080/api/download
Content-Type: application/json

{
  "source": {
    "ip": "192.168.100.11",
    "port": 50711,
    "file": "source.dat"
  },
  "destination": {
    "file": "/parent/destination.dat"
  }
}</code></pre>
<h3 id="response">Response</h3>
<p>Fireball uses custom HTTP response headers ("Error-No", "Error-Message") to share detailed error status.</p>
<pre><code>Error-No: 1
Error-Message: The file does not exist.</code></pre>
<p><img src="https://velog.velcdn.com/images/joosing/post/328c1356-84ac-430c-8490-6e603fb01cc5/image.png"></p>
<h2 id="design">Design</h2>
<p>Fireball sends a large file by splitting them into a series of small chunks (5 MB). On the receiving end, it receives one chunk from the network, buffers it in memory, and then writes it to the file at a time. To do this, We configure the following application message protocol:</p>
<ul>
<li>length: chunk message length (length from id to the end of the chunk contents)</li>
<li>id : Message ID</li>
<li>chunk type : Indicates the position of the chunk in the file (start, middle, end)</li>
<li>chunk contents : contents of chunk file</li>
</ul>
<p><img src="https://velog.velcdn.com/images/joosing/post/41148027-ede3-40e1-947b-7aac36a06fcd/image.png"></p>
<h2 id="-fireball">🏀 Fireball</h2>
<p>The concept of “fast” goes well with the concept of “fire”. I thought the concept of sending a "file" would also fit well with throwing a "ball". The reason why I chose basketball among various balls is not only because I like it, but also because it expresses the concept of the project well. A basketball is heavier than a baseball or other balls. So it's not easy to throw far away quickly. The Fireball project wants to transfer large files like this basketball as fast as blazing fast.</p>
<h2 id="plan">Plan</h2>
<p>The Fireball project is prioritizing the following tasks:</p>
<ul>
<li>Build valuable unit test suites</li>
<li>Support file deletion APIs</li>
<li>Channel encryption and user authentication</li>
<li>Support batch file processing APIs</li>
</ul>

<p>Please feel free to let me know if you have any problems using it, or if you have any suggestions for how to make it better. I'd love to know more about the problems or needs you have in the field, and to make Fireball better for you. And I'm available for full-time work anywhere in the world if you need similar types of work or collaboration. (I'm also available for remote work.)</p></div></div>

Joo's Work

JooSing

🚩 GitHub Link
Overview
The Fireball project provides a small, independent service for quickly transferring large files. No matter what language or framework you use, you can quickly exchange files with a remote location via a simple HTTP request.
Method: POST
URL: http://localhost:58080/api/upload
Content-Type: application/json
{
  "source": {
    "file": "source.dat"
  },
  "destination": {
    "ip": "127.0.0.1",
    "port": 50711,
    "file": "destination.dat"
  }
}
Problem
Anyone can easily write code to exchange files over a network. However, depending on which tool you use and how well you optimize it, there is a big difference in processing performance.
Many Methods, Difference Performance
I tested sending a 1GB file over a loopback network using several representative methods (including Fireball). After 50 iterations of the test, the average was measured, and a typical performance home laptop (Acer Swift 5 Notebook) was used for the test. The time for one measurement includes the time from reading the file, sending it to the network, saving the received file again, and until the response is complete. In the test results below, you can see that even though we're processing the same file under the same conditions, which method we use makes a big difference in performance.
Goal
In above tests, Fireball is not the best performing method, the best performance is achieved by bringing up a Windows FTP server and using the .NET API. The Fireball project will continue to push for better performance in the future. In addition, we want to provide the following core values together.
Small, independent service focused on file transfer.
Service that can be used in any language, any framework, any platform.
Simple programming API.
Single application that integrates the server and the client.
Build
Fireball is a Spring Boot project and uses Maven as its build tool. You can now clone the project, navigate to the root path (where the mvnw file exists), and build the project using the maven wrapper (mvnw). The build result file exists in ./target/fireball-0.0.1.final.jar.
> git clone https://github.com/joosing/fireball.git
> cd fireball
> chmod 744 mvnw
> ./mvnw clean package -DskipTests
Install
To use Fireball to exchange files between different network hosts, the Fireball service must be installed and running on both hosts.
First, make sure you have the Java 17 version installed.
> java --version 
Copy the built JAR file to the desired path.
> cp ./target/fireball-0.0.1.final.jar /app/fireball/fireball-0.0.1.final.jar
Run
Run the Fireball with the following settings
file.client.root : Specify the path to the file root on the client (required)
file.server.root : Specify the path to the file root on the server (required)
server.port : Specify the API server port (Optional, uses port 58080 if not specified)
file.server.port : Specify the file server port (Optional, uses port 50711 if not specified)
> java -Dfile.server.root="/app/files" -Dfile.client.root="/app/files" -jar fireball-0.0.1.final.jar
Usage
Fireball provides two REST APIs for file upload and download. Here is an example of a system configured using Fireball. In this example, the user service is installed on host A (192.168.10.10), and the Fireball service is installed on hosts B (192.168.100.10) and C (192.168.100.11). User sends a file exchange request to Host B. In this case, the Fireball service on Host B will be in the file client role and Fireball on Host C will be in the file server role. The following sections describe example requests that perform file uploads and downloads between Hosts B and C within this configuration.
A. Upload
You can upload a file from Host B to Host C with a simple HTTP request like the following. The example uploads the source.dat file on host B to the /parent/destination.dat file on host C. Each file path is relative to the set root path. If the /parent directory does not exist, it will automatically create it and if the destination.dat file already exists, it will overwrite the existing file and create a new one.
Method: POST
URL: http://192.168.100.10:58080/api/upload
Content-Type: application/json
{
  "source": {
    "file": "source.dat"
  },
  "destination": {
    "ip": "192.168.100.11",
    "port": 50711,
    "file": "/parent/destination.dat"
  }
}
B. Download
You can download files from host C to B with a simple HTTP request like the following. The example downloads the source.dat file on host C to the /parent/destination.dat file on host B. Each file path is relative to the set root path. If the /parent directory does not exist, it will automatically create it, and if the destination.dat file already exists, it will overwrite the existing file and create a new one.
Method: POST
URL: http://192.168.100.10:58080/api/download
Content-Type: application/json
{
  "source": {
    "ip": "192.168.100.11",
    "port": 50711,
    "file": "source.dat"
  },
  "destination": {
    "file": "/parent/destination.dat"
  }
}
Response
Fireball uses custom HTTP response headers ("Error-No", "Error-Message") to share detailed error status.
Error-No: 1
Error-Message: The file does not exist.
Design
Fireball sends a large file by splitting them into a series of small chunks (5 MB). On the receiving end, it receives one chunk from the network, buffers it in memory, and then writes it to the file at a time. To do this, We configure the following application message protocol:
length: chunk message length (length from id to the end of the chunk contents)
id : Message ID
chunk type : Indicates the position of the chunk in the file (start, middle, end)
chunk contents : contents of chunk file
🏀 Fireball
The concept of “fast” goes well with the concept of “fire”. I thought the concept of sending a "file" would also fit well with throwing a "ball". The reason why I chose basketball among various balls is not only because I like it, but also because it expresses the concept of the project well. A basketball is heavier than a baseball or other balls. So it's not easy to throw far away quickly. The Fireball project wants to transfer large files like this basketball as fast as blazing fast.
Plan
The Fireball project is prioritizing the following tasks:
Build valuable unit test suites
Support file deletion APIs
Channel encryption and user authentication
Support batch file processing APIs
Contact
Please feel free to let me know if you have any problems using it, or if you have any suggestions for how to make it better. I'd love to know more about the problems or needs you have in the field, and to make Fireball better for you. And I'm available for full-time work anywhere in the world if you need similar types of work or collaboration. (I'm also available for remote work.)

Fireball: High-performance large file transfer open source project

댓글