A download can become a chargeable event for 2 times the actual file size if the gateway is running on another cloud provider. We recommend interfacing with the network directly through the Uplink Library.
trying to make sense to this… how will it be 2 times charge ?
It depends on where you deploy your gateway. Keep in mind that the gateway will have ingress and egress traffic and depending on where you run it that might get expensive.
I was planning to run on my data center. While my remote server can point to it in remote office.
I still can’t really get the idea where Ingress and Egress bandwidth utilization usage…
I think the meaning is: If you deploy the gateway at a cloud hosting where you also have to pay for traffic you’ll be charged twice. Once for the traffic to the gateway (cloud hoster) and another time for the traffic to the storj network.
thats probably true if i put in azure or AWS…
over at my datacenter, we got unmetered 100Mbps bandwidth… i guess that should still be ok.
furthermore, we do have SNO of 1TB there too …
so just to conclude, it should be ok to put a internet facing gateway as we dont have bandwidth restriction here… only bandwidth which is going to the storj network will be taken count …
Keep in mind that if multiple end users/systems will use this gateway it can become a bottleneck as everything needs to run through this server. You miss out on the bandwidth advantages of having every individual system connect to the nodes directly for transfers.
The warning indeed refers to situations where the server running the gateway would be charged for bandwidth. Since that’s not the case in your scenario, you don’t need to worry about that.