3 ms·

> I couldn't disagree with more from a hands on practical perspective. That will 100% take anyone longer to spin up for an MVP (for more cost) than spinning up

> I couldn't disagree with more from a hands on practical perspective. That will 100% take anyone longer to spin up for an MVP (for more cost) than spinning up a FreeBSD server and I'm unaware of anything that needs more than that for an MVP. I agree with OP. If you hand me a binary and instructions on how to run it, I can have it running on either AWS or DO in a container, connected to a managed database with snapshots enabled in about 30 minutes. If the toolchain is easy to set up, I can have CI/CD with 0-downtime deployments with auto-rollback in another 30 minutes, and you won't need to touch either of those until you're hitting thousands of concurrent users for a typical web app. > you are not only telling them what kind of data you have (don't pretend like the hosts don't know and can't tell) this is FUD of the n'th degree - if you suspect AWS are spying on your managed RDS data, I don't know what to tell you.

AndrewKemendo 4y ago
Great…So you quickly put yourself in a position where the longer you’re on the service the more expensive it will be to migrate And yes Amazon uses AWS utilization to keep track of promising startups or places that they want signal about market changes.
- maccard 4y ago
  > Great…So you quickly put yourself in a position where the longer you’re on the service the more expensive it will be to migrate With 30 minutes work, I've set up a production quality solution that I won't have to touch for months/years, and has almost no vendor lock-in. Containers are portable, you can run them on AWS, DO, GCP, or install docker on a bare metal instance, it's up to you. Until you _do_ decide to migrate, it's pretty much 0 upkeep (I checked one of the work projects I stood up and we haven't touched the infrastructure side of it for 9 months). > And yes Amazon uses AWS utilization to keep track of promising startups or places that they want signal about market changes. That's not what you said at first, you said "you are not only telling them what kind of data you have (don't pretend like the hosts don't know and can't tell)". You're telling AWS that you're running containers and a database.
  - scarface74 4y ago
    Yes, and I’m sure after you set things up with “no vendor lock in”, you came back years later when the company grew and organized a large migration where you had to deal with budgets, transferring data, regression testing, going through architecture review boards, the PMO, permissions, compliance, training, etc. I’m also sure after many years no vendor specific corner cases snuck in that you didn’t realize were there

AndrewKemendo 4y ago

Great…So you quickly put yourself in a position where the longer you’re on the service the more expensive it will be to migrate And yes Amazon uses AWS utilization to keep track of promising startups or places that they want signal about market changes.

maccard 4y ago
> Great…So you quickly put yourself in a position where the longer you’re on the service the more expensive it will be to migrate With 30 minutes work, I've set up a production quality solution that I won't have to touch for months/years, and has almost no vendor lock-in. Containers are portable, you can run them on AWS, DO, GCP, or install docker on a bare metal instance, it's up to you. Until you _do_ decide to migrate, it's pretty much 0 upkeep (I checked one of the work projects I stood up and we haven't touched the infrastructure side of it for 9 months). > And yes Amazon uses AWS utilization to keep track of promising startups or places that they want signal about market changes. That's not what you said at first, you said "you are not only telling them what kind of data you have (don't pretend like the hosts don't know and can't tell)". You're telling AWS that you're running containers and a database.
- scarface74 4y ago
  Yes, and I’m sure after you set things up with “no vendor lock in”, you came back years later when the company grew and organized a large migration where you had to deal with budgets, transferring data, regression testing, going through architecture review boards, the PMO, permissions, compliance, training, etc. I’m also sure after many years no vendor specific corner cases snuck in that you didn’t realize were there