One of the worst blunder of my recent career is not pushing against amplify enough.
I know it is not cool to diss on others' work, but amplify is so wrong on so many level (for my use case) it really is painful.
Want to go off the main road? Sure you can sometimes, but it will break (low code tools are just the wrong abstraction for a dev). Want you to deploy different env in different subaccount? you can but we will make your life miserable. Want to keep your auto generated cognito lambdas on up to date runtimes? can't help you. Want to use custom resources? yeah, however, we will probably mangle your project. Want to add cognito on your front end? Sure, I hope you don't like your app lightway.
Want you use graphql? sure but we will use dynamodb in a way that will make Rick Houlihan cry.
In the end it wasn't the right tool for us, but it sure was attractive for our management. V2 position itself as "code first", so I think they've got the memo. However, I'll still setup a CDK project next time, where you actually can control what happens.
What is the worst AWS service? I vote for Amplify
21–23 of 23 posts
Re: What is the worst AWS service? I vote for Amplify
#22Pretty much the entire AWS Code* stack: CodeCommit, CodeBuild, CodeDeploy ... Does any developer use those willingly? Also SAM. I run into a new bug or limitation in SAM every other time I touch it. Really need to ditch it for CDK.
I use CodeBuild and CodePipeline. I love these products. I use them via CDK so maybe it’s better DX that way.
Re: What is the worst AWS service? I vote for Amplify
#23This article is in Chinese for me, is it just me?
Yeah lol I wasn't confused that the article was in Chinese, I was confused that people were just discussing it casually as though it were plain English. "Is there a translated version of this that I'm missing somewhere?" But that's just HN, most people comment on the headline without even clicking the link.
Haha, yeah, that's what threw me off too, I saw the comments and thought I must be missing something.