3 ms·
Those costs only apply to data transfer into and out of AWS. If you're running EC2 instances in AWS, your Regatta file system is in AWS, and your S3 bucket is i
by huntaub 2y ago
Those costs only apply to data transfer into and out of AWS. If you're running EC2 instances in AWS, your Regatta file system is in AWS, and your S3 bucket is in AWS -- then you shouldn't incur additional data transfer fees.
- discodave 2y agoWhere you say AWS, you mean "a single AWS region" But anyway, from your YCombinator blurb: "When you’re done editing data, it automatically flows back to S3 within a few minutes" Does this mean Regatta trades consistency for cost (S3 and EBS and local storage are all CP systems these days)?
- huntaub 2y agoYes, that's correct re: Region -- thanks for the clarification. In some sense, yes. But, the consistency that you're trading is only for accessing data simultaneously through the file interface and the S3 interface simultaneously. The consistent is CP/strong when you access the data through the file interface. The model that we see most often work is folks will ingest data through S3 (for example, an 'input/' prefix), and then the file system will process that data and place it in a different directory (for example, an 'output/' folder). Then, if it takes a minute or two for those to update on the other side, it's not a big deal.
- ec109685 2y agoIt async replicates to s3, while providing a consistent interface to storage clients.