3 ms·
Yeah, I think people just don't fully realise how powerful hardware has become. You don't need complicated tools if you need to transfer even significantly larg
by nasretdinov 2y ago
Yeah, I think people just don't fully realise how powerful hardware has become. You don't need complicated tools if you need to transfer even significantly large amounts of data, since you can have hundreds of gigabits of network capacity on a single server, so unless you're truly large you probably can get away with using vanilla rsync for file transfers for example :).
- waych 2y agoManaged async bulk transfers as-a-service seems relevant to anyone writing lots of data doing multisite including DR. You can easily have this problem and not have yet hit any other scale problems that are addressed by the alluded-to tools people love to hate (k8s, tf, containers etc). What is being managed here with Effingo is the relatively tiny links between sites, not the bandwidth on the fat local links. Bandwidth needs to be managed and prioritized across all the various copies that are happening across different services apps and teams simultaneously across the company, and across the systems themselves as aggregate for the links. Managing it gives you control on cost but also ensures optimal use within the constraints imposed and consistent and reliable handling of the copy use case.