AWS Amplify Is a Grift

Re:AWS Amplify Is a Grift by ramblinrose on Monday April 10, 2023 @02:55PM (#35515944)

I use Amplify for a mobile app that I created and maintain just because I'm not familiar with backend technologies and it seemed like the quickest and easiest option for me, a mobile developer. The app isn't super complex, but I wouldn't describe it as a "toy" application either. I haven't run into any major headaches with DynamoDB or GraphQL limitations... yet.

But this article has me thinking about exploring other options. To try to get ahead of the seemingly inevitable wave of tech debt. Does anyone have advice or can point to any resources for embarking on that particular journey? Are there similar technologies that do it better than Amplify? Anything in between Amplify and learning all the disparate AWS tools from scratch?

[ Parent | on HN ]

Re:AWS Amplify Is a Grift by spmurrayzzz on Monday April 10, 2023 @03:55PM (#35516656)

> Anything in between Amplify and learning all the disparate AWS tools from scratch?

It depends how much of the backend you ultimately would like to avoid (and related to that, how complex your service ecosystem will be for your app).

Without knowing much more about your app, I can throw some darts. You could use RDS to get you postgres/maria/etc and then just run an app server on EC2 for your backend REST/SOAP/etc API in front of that. If the latter body of work isn't comfortable for you, there is a swath of low code tooling out there you could use as well to put an API in front of your SQL for you (nocodb comes to mind, or just postgrest if all you need is CRUD ops).

[ Parent | on HN ]