A question on Twitter (<a href="https:&#x2F;&#x2F;twitter.com&#x2F;sayhar&#x2F;status&#x2F;671867539480305664" rel="nofollow">https:&#x2F;&#x2F;twitter.com&#x2F;sayhar&#x2F;status&#x2F;671867539480305664</a>) asked about how Simple decided to do ETL in Redshift.<p>I think the main benefit is flexibility. Since transformations are happening in the same system where the data already lives, there&#x27;s no I&#x2F;O overhead and the performance is pretty fast. Our full suite of nightly ETL jobs runs in about 2 hours, and that&#x27;s without any effort to run jobs in parallel. There&#x27;s also minimal schema maintenance involved; the nightly jobs completely drop the existing tables, and in most cases the table creation is handled automatically as part of a CREATE TABLE AS statement. That means we&#x27;re pretty free to add, drop, or rename columns without needing to worry about migrations or keeping the schema in sync with what some external tool is doing.<p>That said, no one on our team has deep familiarity with ETL tools, so there may be other good options that we simply haven&#x27;t investigated.