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?
Why do you say that? In my comment I'm rooting for you. I did say that you should have mentioned this is a counter-suit to your own suit, and I stand by that. Why omit that information? Or is that a misunderstanding?
Thanks for sharing this. It looks like Impossible X (the defendant) was the first to sue to have Impossible Foods cease using their logo and trademark. And now Impossible Foods isn't budging and asserting their weight through counter-suit. It still feels very unfair even though the small guy started it; he's trying to protect his brand. He has supplied actual cases of confusion between the two companies according to this filing.
He should have definitely included that information in this blog post though. It's more than a little misleading.
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?