Amazon AppFlow • Hacker News Board

Re: Amazon AppFlow

#11

Post by amelius » Thu, Apr 23, 2020, 10:21 PM UTC

masonhensley wrote: post #3

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.

Which is kind of curious because they only move data from app A to app B. Makes you wonder how much engineering effort it would take to actually do something with the data.

Re: Amazon AppFlow

#12

Post by i_am_nomad » Thu, Apr 23, 2020, 10:26 PM UTC

seibelj wrote: post #9

This seems like a Zapier killer, makes sense.

I’m not so sure about that - Zapier has a number of use cases that are completely unrelated to AWS.

Re: Amazon AppFlow

#13

Post by jedberg » Thu, Apr 23, 2020, 10:31 PM UTC

> Hydrate data lakes

The power of metaphor right there. Although I've never seen that phrase before, I know exactly what it means.

Re: Amazon AppFlow

#14

Post by lilfermat » Thu, Apr 23, 2020, 10:36 PM UTC

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 a potential cost saver for us in the longer. It’s exciting to see more competition in this space none the less.

Re: Amazon AppFlow

#15

Post by dehumanise » Thu, Apr 23, 2020, 10:36 PM UTC

degenerate wrote: post #8

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?)

Re: Amazon AppFlow

#16

Post by scottlamb » Thu, Apr 23, 2020, 10:36 PM UTC

jedberg wrote: post #13

> 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.

Re: Amazon AppFlow

#17

Post by basch » Thu, Apr 23, 2020, 10:39 PM UTC

How does this compare to

Azure Data Factory https://azure.microsoft.com/en-us/services/data-factory/

and

Microsoft Power Automate - https://flow.microsoft.com/

Re: Amazon AppFlow

#18

Post by Calcite » Thu, Apr 23, 2020, 10:39 PM UTC

i_am_nomad wrote: post #12

seibelj wrote: post #9

This seems like a Zapier killer, makes sense.

I’m not so sure about that - Zapier has a number of use cases that are completely unrelated to AWS.

This is just Amazon’s first move. They definitely have most of Zapier’s use cases on their roadmap at this point.

Re: Amazon AppFlow

#19

Post by krackers » Thu, Apr 23, 2020, 10:40 PM UTC

scottlamb wrote: post #16

jedberg wrote: post #13

> 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.

Hydrate would imply that what you currently have sitting is "dehydrated" in some form.

Re: Amazon AppFlow

#20

Post by howmayiannoyyou » Thu, Apr 23, 2020, 10:43 PM UTC

Integromat Parabola CloudHQ Zapier Apache Nifi ... and literally dozens more.

Very, very crowded space.