AWS Amplify Is a Grift

Re:AWS Amplify Is a Grift by badrequest on Monday April 10, 2023 @02:00PM (#35515244)

There are two sides to this arrangment: devs who mostly don't have a choice over the tools they use vs. the trillion-dollar company that is building and documenting them. The notion that the devs have just as much culpability in how things end up as AWS is absurd.

[ Parent | on HN ]

Re:AWS Amplify Is a Grift by ctvo on Monday April 10, 2023 @02:39PM (#35515755)

> devs who mostly don't have a choice over the tools they use

I'm not going to assume that DynamoDB was forced upon them. I don't know. What I'm more sure about:

Developers have a choice in if they want to invest the time in understanding the tools they use, and learning about the tool's capabilities. In this specific case, we're not talking about a lot of time. 2-3 hours to read the documentation for a new database you're going to be building your business on top of.

What is your argument exactly?

[ Parent | on HN ]

Re:AWS Amplify Is a Grift by icedchai on Tuesday April 11, 2023 @09:57AM (#35525207)

I've personally seen developers "forced" into using DynamoDB because some AWS professional services consultant suggested it. You could argue the developers should've known better, but they had relatively little real world experience. The costs of Dynamo are relatively small compared to the development costs of using it when it's not a good fit.

[ Parent | on HN ]