3 ms·
One of our engineer's recently floated up the idea of using ToroDB Stampede for replacing our MongoDB -> PostgreSQL ETL, since it's merely a set of Python scrip
by kasano 10y ago
One of our engineer's recently floated up the idea of using ToroDB Stampede for replacing our MongoDB -> PostgreSQL ETL, since it's merely a set of Python scripts parsing JSON into tables.
Have you seen use cases of Stampede being implemented on existing databases/schemas, rather than an entirely new DB?
- ahachete 10y agoHi kasano. One of the most relevant use cases of ToroDB Stampede is precisely what you say, replacing MongoDB to PostgreSQL ETLs, where you have to design the schema, solve data type conflicts, maybe flatten or discard data, etc. And other problems like real-time replication, managing HA, etc. Stampede addresses all these problems. While most people may want to use an empty, dedicated database for Stampede, it is not required to do so. Stampede will generate the tables under a schema name that matches the collection name. So as long as there are no name conflicts, you can happily have ToroDB-generated tables alongside your own. Needless to say, this gives you the ability to JOIN information from different data sources. So sure, go and give it a try! :)