Similar thoughts (btw I came here looking for your comment ha!).
I guess you had mentioned in one of the videos that at Fivetran, it is your responsibility to ensure data integrity across all of the sources/integrations, and has been since the early days. This led the customers to trust the product in the early days and the team to draw learnings from abstract patterns across sources.
Have come to believe that it is THE MOST important thing to have an explicit ownership for issues whenever there is physical movement of data across an org's ecosystem.
Yes, a mix of 1 & 2 possibly -- am trying not to think too much about the implementation at this stage tbh.
Problem statement remains that every major SaaS app has an API available - while that's good, an API is still an engineer's tool. These apps can't really expose SQL on the go on their apps given a. multi-tenant architectures b. transactional/nosql databases used.
However, an ideal solution does seem like a mix of 1&2 in my mind. An easy to use SDK (?) to make any SaaS app have the capabilities of Stripe Sigma.
If I am looking to build an MVP and assuming that I can learn both native and React/Flutter like frameworks -- which one would you suggest based on the learning curve in both?
I guess you had mentioned in one of the videos that at Fivetran, it is your responsibility to ensure data integrity across all of the sources/integrations, and has been since the early days. This led the customers to trust the product in the early days and the team to draw learnings from abstract patterns across sources.
Have come to believe that it is THE MOST important thing to have an explicit ownership for issues whenever there is physical movement of data across an org's ecosystem.