Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Amazon AppFlow

aws.amazon.com

Post reply on HN
Print view View original

61–70 of 112 posts

Re: Amazon AppFlow

#61

Post by kull »

hanniabu wrote: post #38
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.

What are some good Jira alternatives? We use Trello, but it's limited and plugins are needed for everything.

Youtrack

Re: Amazon AppFlow

#62

Post by dataminded »

zmmmmm wrote: post #55

I really wonder about all these services that eat into the layers of implementation that organisations usually do in house, but at the same time quick form a complex web of lock in that prevents you ever leaving Amazon. It seems to me that these services are very seductive but there are very few cases where it's truly in an organisation's long term interest to adopt them. At best, use them as a quick interim solution…

Why do you worry about vendor lock-in?

If you get to a point where you are locked-in it's because you spent years building into a solution that was your most expedient and renumerative option. At some future point in time, a future you or the person who replaces you may want to reconsider a re-platform. Let them worry about that.

I worry about development working on glue code/solve problems to the detriment of their businesses actual needs.

Re: Amazon AppFlow

#63

Post by Aperocky »

hanniabu wrote: post #38
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.

What are some good Jira alternatives? We use Trello, but it's limited and plugins are needed for everything.

> it's limited

Isn't that the point? Businesses and people are way more obssessed about Jira than they should ever be. Jira is supposed to help organize, not become someones job.

Re: Amazon AppFlow

#64

Post by shard972 »

dataminded wrote: post #62
zmmmmm wrote: post #55

I really wonder about all these services that eat into the layers of implementation that organisations usually do in house, but at the same time quick form a complex web of lock in that prevents you ever leaving Amazon. It seems to me that these services are very seductive but there are very few cases where it's truly in an organisation's long term interest to adopt them. At best, use them as a quick interim solution…

Why do you worry about vendor lock-in? If you get to a point where you are locked-in it's because you spent years building into a solution that was your most expedient and renumerative option. At some future point in time, a future you or the person who replaces you may want to reconsider a re-platform. Let them worry about that. I worry about development working on glue code/solve problems to the detriment of their…

And this is why oracle and IBM still exist.

Re: Amazon AppFlow

#65

Post by JimDabell »

hanniabu wrote: post #60
endgame wrote: post #49

Earlier quoted context omitted.

Trello's the one that rolls random people's personal accounts into the account of the business they work for, right? And refuses to give them back when asked?

I don't think I've experienced this issue.

This is what endgame is referring to:

> Trello handed over my personal account to my previous company

— https://news.ycombinator.com/item?id=22873578

Re: Amazon AppFlow

#66

Post by hobofan »

dataminded wrote: post #62
zmmmmm wrote: post #55

I really wonder about all these services that eat into the layers of implementation that organisations usually do in house, but at the same time quick form a complex web of lock in that prevents you ever leaving Amazon. It seems to me that these services are very seductive but there are very few cases where it's truly in an organisation's long term interest to adopt them. At best, use them as a quick interim solution…

Why do you worry about vendor lock-in? If you get to a point where you are locked-in it's because you spent years building into a solution that was your most expedient and renumerative option. At some future point in time, a future you or the person who replaces you may want to reconsider a re-platform. Let them worry about that. I worry about development working on glue code/solve problems to the detriment of their…

Vendor lock-in is just another form of technical debt and should be treated as such.

Sure right now it's your easiest option, but in the future the vendor might be the only one offering a compatible version of CoolNewFeatureXY at prices that make your business uncompetitive to the other businesses that have the freedom to choose between vendors.

Re: Amazon AppFlow

#67

Post by 0x6c6f6c »

degenerate wrote: post #22
dehumanise wrote: post #15

Earlier quoted context omitted.

just curious, why is it horrible for tasking? (and what alternative would you consider not-so-horrible?)

Jira is good for tasking, but has a clunky UI and is riddled with bugs. I mean horrible because Atlassian made it.

Of their products, Jira does surprisingly well for us. I dislike quite a few of their products but Jira just works for us, though some things seem to be more work than necessary to do. Some of that can be blamed on company processes though.

Re: Amazon AppFlow

#68

Post by scottlamb »

jedberg wrote: post #26
scottlamb wrote: post #16

Earlier quoted context omitted.

Does "hydrate" add some nuance here that "fill" doesn't? If so, I'm missing it.

An empty lake can be filled with lots of stuff, like trash. But if you hydrate it then you are specifically filling it with water. Also it just sounds cooler.

I specifically meant nuance relating to the product as well as actual lakes. If there's none, the word choice (and maybe the whole metaphor) is a distraction.

Also, as I mentioned in another comment, this phrase doesn't work for the metaphor. Dehydrating and rehydrating a lake isn't a good idea; it'd kill the ecosystem, and it'd be tremendously expensive. I'd rather stick to dehydrating and rehydrating something else, like fruit. Here, this looks similar to the fruit soup my in-laws make: https://www.cheaprecipeblog.com/2015/11/norwegian-sweet-soup...

Re: Amazon AppFlow

#69

Post by ryanmarsh »

zmmmmm wrote: post #55

I really wonder about all these services that eat into the layers of implementation that organisations usually do in house, but at the same time quick form a complex web of lock in that prevents you ever leaving Amazon. It seems to me that these services are very seductive but there are very few cases where it's truly in an organisation's long term interest to adopt them. At best, use them as a quick interim solution…

use that as your requirements for an open source or at least vendor-neutral equivalent

My clients are all expending far too much energy trying to be cloud vendor neutral with the engineering capacity of your average non-tech large mid-market company. It's killing productivity. They went from VMWare in the data center and open source DevOps tooling to multi-cloud vendor-agnostic container-orchestration all in the name of "cloud but not with vendor-lock in". Meanwhile they could be actually achieving business objectives with these "seductive" managed services.

Here's one simple example, one client is spending about $250,000/yr on what could be accomplished with AWS Cognito for $250/month. But "no", they say, "then we'd be locked in to AWS".

I just can't.

Re: Amazon AppFlow

#70

Post by JimDabell »

Calcite wrote: post #18
i_am_nomad wrote: post #12

Earlier quoted context omitted.

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.

Amazon seem to have a disadvantage here though. This kind of tool is aimed at non-developers who want to glue stuff together. With Zapier, they register an account and get stuck in – straightforward. With AWS, they register an account and are instantly overwhelmed with a million different things. AWS is too big and unfocused for the target market. I've seen developers hit a wall once they get on board AWS because it's just too much to deal with. You think the AWS dashboard is any friendlier to non-developers?
Post reply on HN