Metropolis got deprecated (read renamed) Foundry because they kept screwing up their sales and decided a rebrand would be more effective on their commercial side.
Foundry started as our attempt to create scalable process and rigor around data integration. There's a longer story to tell here, but the short version is that we started out with off-the-shelf orchestration systems for running jobs on a schedule (think Jenkins and Rundeck — things that were more robust than cron). At some level, that worked, and we had to figure out how to scale it, leading to a combination of HDFS, Rundeck/Jenkins, a git repo, and a common language for mutating data.
Metropolis got deprecated (read renamed) Foundry because they kept screwing up their sales and decided a rebrand would be more effective on their commercial side.
https://www.quora.com/What-are-the-main-differences-between-...
per someone who runs tech on the commercial side,
Foundry started as our attempt to create scalable process and rigor around data integration. There's a longer story to tell here, but the short version is that we started out with off-the-shelf orchestration systems for running jobs on a schedule (think Jenkins and Rundeck — things that were more robust than cron). At some level, that worked, and we had to figure out how to scale it, leading to a combination of HDFS, Rundeck/Jenkins, a git repo, and a common language for mutating data.