21–30 of 112 posts
Earlier quoted context omitted.
Does "hydrate" add some nuance here that "fill" doesn't? If so, I'm missing it.
Hydrate would imply that what you currently have sitting is "dehydrated" in some form.
The full list of SaaS integrations: https://aws.amazon.com/appflow/integrations/ Amplitude, DataDog, Dynatrace, Google Analytics, Infor Nexus, Marketo, Salesforce, ServiceNow, Singular, Slack, Snowflake, Trend Micro, Veeva, Zendesk. I feel like a notably missing product from this list is Jira. As horrible as it is, lots of companies use Jira for tasking so it should have been supported out the gate.
just curious, why is it horrible for tasking? (and what alternative would you consider not-so-horrible?)
By now - the amount of time teams have spent doing this sort of work from scratch has to have surpassed the engineering hours taken to get to the moon.
I've built a few projects that provide real-time reporting across sass applications but it always seems like an uphill battle. Especially when your only interface with the sass is a hypertext API.
Can a data source change while you're completing a multi-part query? Are records hard deleted? If so how do you detect removed records to maintain deltas? How do you maintain deltas throughout lossy pipelines that group or filter?
In the end, it always feels like it'd be easier to build one monolith to replace all the systems and report on that instead...
The full list of SaaS integrations: https://aws.amazon.com/appflow/integrations/ Amplitude, DataDog, Dynatrace, Google Analytics, Infor Nexus, Marketo, Salesforce, ServiceNow, Singular, Slack, Snowflake, Trend Micro, Veeva, Zendesk. I feel like a notably missing product from this list is Jira. As horrible as it is, lots of companies use Jira for tasking so it should have been supported out the gate.
> Hydrate data lakes The power of metaphor right there. Although I've never seen that phrase before, I know exactly what it means.
Does "hydrate" add some nuance here that "fill" doesn't? If so, I'm missing it.
Also it just sounds cooler.
This seems like a Zapier killer, makes sense.
> Hydrate data lakes The power of metaphor right there. Although I've never seen that phrase before, I know exactly what it means.
Does "hydrate" add some nuance here that "fill" doesn't? If so, I'm missing it.
I also smirked at the metaphor. The AWS marketing department must be high fiveing right now
This is an interesting addition to AWS! I wonder how is this better than stitch or fivetran? It’s not immediately clear to me. Also I am doing the back the envelope math. It seems like app flow cost more than our current usage of stitch or even fivetran to our redshift warehouse and doesn’t even include some of our bigger other sources we use (MySQL, stripe). I am gonna do more analysis on this and see if this can be…
Is this a Segment type thing?
No, more like https://fivetran.com/ and others like it. (unless Segment has recently pivoted.)