I dislike your sarcastic winky face, but I agree with the sentiment.
Unless you plan on handing amazon your money forever, you should always steer for agnostic solutions you have the ability to host yourself.
As much as it may not 'scale' if you manage to get a passive income with decent understanding of load, then purchasing hardware is almost certainly cheaper for you.
Cheaper is good, it means more return so you can invest that income in your new project (and pay amazon for easy scaling again, if you want). But removing that ability not only locks you into their platform which may change prices at any time... it also means you can't move to self-hosting when the time is right and save quite a lot of money.
I dont believe you are locked in with AWS forever if you choose DynamoDB.
It doesnt use a unique database model that no other DB supports. Its based on NOSQL and it should be simple enough (with effort of course) to export a DynamoDB document store to another NOSQL solution.
your reply makes me believe you've never migrated database solutions for larger projects, especially ones where you're trying to actually make money and spend little time.
Migrating database solutions is really quite expensive in terms of time. I've done it twice and it's not something to take lightly. The usual recommendation is to never migrate database solutions unless there is a catastrophic problem with continuing with the current.
I dislike your sarcastic winky face, but I agree with the sentiment.
Unless you plan on handing amazon your money forever, you should always steer for agnostic solutions you have the ability to host yourself.
As much as it may not 'scale' if you manage to get a passive income with decent understanding of load, then purchasing hardware is almost certainly cheaper for you.
Cheaper is good, it means more return so you can invest that income in your new project (and pay amazon for easy scaling again, if you want). But removing that ability not only locks you into their platform which may change prices at any time... it also means you can't move to self-hosting when the time is right and save quite a lot of money.
I dont believe you are locked in with AWS forever if you choose DynamoDB.
It doesnt use a unique database model that no other DB supports. Its based on NOSQL and it should be simple enough (with effort of course) to export a DynamoDB document store to another NOSQL solution.
your reply makes me believe you've never migrated database solutions for larger projects, especially ones where you're trying to actually make money and spend little time.
Migrating database solutions is really quite expensive in terms of time. I've done it twice and it's not something to take lightly. The usual recommendation is to never migrate database solutions unless there is a catastrophic problem with continuing with the current.
6 replies →
It's a fair point, but when you stick to the same ecosystem you save a lot of time in terms of setup for credentials, monitoring, backups, devops etc.