4 ms·
I value your opinion but I have had a very different experience. 1. I agree. First few attempts at DynamoDB tables were a disaster. But once you get used to th
by throwaway2016a 9y ago
I value your opinion but I have had a very different experience.
1. I agree. First few attempts at DynamoDB tables were a disaster. But once you get used to them you don't have to change schemas and then it is not an issue. Note, you can add and indexes, just not the primary one.
2. Not so. It's not easy but it's far from impossible or painful. I've had my fair share of pain migrating SQL databases too.
... Export to S3
... Grab the S3 backup and write an ETL to format and load it
... Put in place a stream hook to keep your newly loaded database up to date
... Switch over your data abstraction / model layer (you did use one of those right?)
3. You can also choose your indexes wisely. How is this different than a normal database?
Most of my DynamoDB using apps I run for 100% free and I've scaled to hundreds of thousands of users for less than the cost of a small Postgres server.
Just keep a model layer between you and Dynamo to avoid vendor lockin and you'll be fine.