3 ms·

My team (5 engineers, 18 months building so far) currently runs the largest amplify based project in terms of number of resources used. We have a direct connect

My team (5 engineers, 18 months building so far) currently runs the largest amplify based project in terms of number of resources used. We have a direct connection to the core team and their support has been great. Things were quite rough until about 6 month ago. The new releases in version 7.5.x unwind a ton of technical debt that caused serious instability. If I were to start our project over again knowing what I know now I might use SAM or the serverless framework instead of amplify, but I am not sure. The graphQL spec definition to dynamo table feature is the entirety of the magic in amplify IMO, and it has seriously sped up our development time. I strongly recommend against using any of the UI components, or many of the features that appear to be "tacked on the side" because in my experience they are tacked on and don't work well. Happy to answer any questions.

jitl 5y ago
> The graphQL spec definition to dynamo table feature is the entirety of the magic in amplify IMO Can you point me to the "good stuff" in their docs? A brief Google search quest revealed several things that all seemed to be GraphQL to CloudFormation/Dynamo/.. Which one do you use and trust? Is it this thing? https://docs.amplify.aws/cli-legacy/graphql-transformer/overview/#test-the-api https://docs.amplify.aws/cli-legacy/graphql-transformer/over...
- 0xB31B1B 5y ago
  Its everything in the graphql API section: https://docs.amplify.aws/cli/graphql/overview/ https://docs.amplify.aws/cli/graphql/overview/ you create a graphql API spec and amplify builds all of the appsync resolvers and dynamo tables for you. Pretty good support for different auth methods and table schemas. Looking at the newest version of the docs it seems they are indeed deprecating some of the weird niche features and doubling down on the things that already work well.
unbanned 5y ago
How did you end up in such an unlucky situation?

jitl 5y ago

> The graphQL spec definition to dynamo table feature is the entirety of the magic in amplify IMO Can you point me to the "good stuff" in their docs? A brief Google search quest revealed several things that all seemed to be GraphQL to CloudFormation/Dynamo/.. Which one do you use and trust? Is it this thing? https://docs.amplify.aws/cli-legacy/graphql-transformer/overview/#test-the-api https://docs.amplify.aws/cli-legacy/graphql-transformer/over...

0xB31B1B 5y ago
Its everything in the graphql API section: https://docs.amplify.aws/cli/graphql/overview/ https://docs.amplify.aws/cli/graphql/overview/ you create a graphql API spec and amplify builds all of the appsync resolvers and dynamo tables for you. Pretty good support for different auth methods and table schemas. Looking at the newest version of the docs it seems they are indeed deprecating some of the weird niche features and doubling down on the things that already work well.

unbanned 5y ago

How did you end up in such an unlucky situation?