Common Use Cases: Data archive (for infrequent ingress/egress, typical with POC or other rapid, low complexity implementation) This isn’t the optimal configuration for most uses.
Key Implementation Details: Mirrors usage patterns for Amazon S3 being used when Tardigrade replaces existing S3 compatible data stores. Similar to S3 compatible data stores that expose cloud-hosted S3 endpoints located in data centers. The S3 gateway is installed on a web application server in the customer cloud or public cloud and accessed online.
The Gateway is designed to upload/download data to/from multiple storage nodes in parallel. This bittorrent-like parallelism provides a sizable performance boost when transferring data. In this pattern, bandwidth is potentially costly as the data uploaded is ingress to the web server, but then egress from the web server to the Tardigrade Network, including the erasure coding expansion data. Egress from the web server requires data be downloaded to the web app server from the storage network. In this case, egress fees may be incurred both from Tardigrade and the hosting environment.