I've been using AWS Amplify (Gen 1) for my tutoring website for about three years now, but I'm really struggling with its build system lately. It has been okay, managing under 1000 monthly active users, but I'm facing a lot of problems, particularly with the DynamoDB integration that Amplify uses. The way they implement database schema feels more like SQL, yet it's based on NoSQL, creating complexities with foreign keys and data fetching that I just can't keep dealing with. I'm considering whether it's worth the effort to migrate everything over to Supabase or PocketBase, despite my app being of medium size and this potentially being a big hassle for one person. So, is migrating a good idea, or can I find ways to make my current setup work despite its limitations?
3 Answers
I get where you’re coming from with Amplify's issues. If you're drowning in code complexity, maybe simplifying to something like PocketBase is a better fit for your workflows. It’s designed to make self-hosting a breeze and could alleviate a lot of the pain you’ve been experiencing. Consider experimenting with both options to figure out which one gives you the most peace of mind.
I tried Amplify and had my share of frustrations with it. If you're looking for easier migration paths, I'd suggest checking out Cloudflare Pages and Workers. Those are pretty developer-friendly. Their integrated D1 database is a solid choice for SQL needs, plus it’s relatively easy to work with structured queries. However, you might encounter limitations in terms of individual D1 databases for each user, so consider how that fits with your existing data structure.
It sounds like you're really fed up with Amplify's integration, especially with DynamoDB. You're correct that migrating to a new platform could be a significant amount of work, since you'll need to rework your database logic to fit with Supabase or PocketBase. If your app structure and data complexity are manageable, the transition might not be too bad. On the other hand, AWS does have a strong scaling capability. Before jumping ship, consider if you can optimize your current setup, as some developers find a way to make Amplify work for their needs. But if you're leaning towards a migration, just prepare for a bit of refactoring in how you handle your data.
Exactly! While AWS is powerful, its complexity can get overwhelming. If you find certain features aren't really benefiting you anymore, looking at alternatives like Supabase could help simplify things. It might be worth testing both to see which fits better with your needs.
I've heard similar things about D1 and the need for individual databases for each client. It could complicate things if your data is heavily interconnected like in tutoring scenarios. Make sure to weigh that against your current challenges!