AWS Amplify CLI or Serverless Framework for My Situation?

2 points

8 years ago

I used [Serverless](https://serverless.com) before, when I built my last three tier mobile app backend using API Gateway + Lambda + DynamoDB (plus Cognito as AuthN, by the way). And I had a good experience on that route. Back then, I researched both AWS SAM and Serverless, and decided to go to Serverless route (because slightly modifying a tutorial example gives me what I wanted right there).

Now, I am doing my next project, and Amplify CLI is announced.

I think I am going to use AWS Amplify client library regardless for my React App (that is almost decided); but now I am doing the technical decisions between Serverless framework and Amplify CLI [1]. Any experience to share regarding: bug/maturity/pros and cons for either route? - In particular, Serverless gives users the "in total control of your backend architecture" situation, (I have not used Amplify CLI) does Amplify CLI make me lose that level of control (i.e., providing too much abstraction)? - how mature Amplify CLI is from bug hiccup perspective and major capability plugins availability perspective? - What's the learning curve for Amplify CLI?

Thanks for providing your thoughts.

[1] https://hackernoon.com/aws-amplify-7-new-things-for-serverless-63ecad310d9f

3 comments