I thought this was really interesting:

Every SaaS product should offer a plug-and-play thing so that I can copy all the data back into my own SQL-based database (in my case, Postgres/Redshift). I don’t want to use their custom made DSL. Maybe European Union can mandate this as the next step after their PSD2 open banking directive.

I think the answer here is “build an extendable singer tap with your SaaS product” which is something that I’ve heard Douwe mention a couple of times https://erikbern.com/2018/08/30/i-dont-want-to-learn-your-garbage-query-language.html

love it! This stuff has been on my mind actually a lot. I recently wrote about how SQLAlchemy + Python DB-API 2.0 lets Apache Superset support a lot of database. But inherent in this bet + complexity by that open source community is that every database is slightly different in their query language ><

We’d love to see companies support their own Singer Tap. Data Portability is essential 👍

yeah for sure, I’m guessing its against most companies interests though (esp those that benefit from network effects)

I expect it’s going to be a feature that more customers demand. I know when I was helping folks kick the tires on different saas offerings we strongly advocated for tools that would enable us to get the data out somehow so that we could analyze and integrate it. But they all do it in so many weird ways (here’s an API, here’s an S3 bucket we dump to nightly, etc.). I want part of the journey of Meltano is to elevate data awareness at the corporate level so people demand more from their tools 🙂

yeah for sure, thats cool! I could see a nice Meltano blog post laying out some standards / hierarchy of awesomeness

“hierarchy of awesomeness” I love it 😄

level 1 is like dirty data dump thats undocumneted lol. level 5 is a nice clean api you can hammer with constraints clearly spelled out, versioned documentation, blah blah

@srini_kadamati__apache_superset_ do you want to open an issue and get the ball rolling?

will do