←back to thread

325 points davidbarker | 7 comments | | HN request time: 0.957s | source | bottom
1. amelius ◴[] No.44386047[source]
Remember, folks: don't build your castle in someone else's kingdom.
replies(2): >>44387060 #>>44388577 #
2. owebmaster ◴[] No.44387060[source]
That's not a great advice, actually. Don't build just one castle and extract all value from the kingdom to your castles outside of it.
replies(1): >>44387132 #
3. amelius ◴[] No.44387132[source]
That's ... a lot of work. If you have that kind of resources you might as well play an entirely different game.
4. socalgal2 ◴[] No.44388577[source]
Yep, no one builds anything in the kingdom of AWS
replies(1): >>44389455 #
5. amelius ◴[] No.44389455[source]
AWS is more like a commodity service, relatively easily swapped for something else.
replies(2): >>44389537 #>>44390046 #
6. BozeWolf ◴[] No.44389537{3}[source]
… if you only run a few (micro)services on a few dozen machines.

Whole enterprises run everything in the cloud. 1000s of vms. From active directory, dns, virtual desktops until “lift and shift” legacy apps. And also a lot of networking to make the company networkwork with aws…

And that is only the technical aspect of it.

Migrations take years.

7. srmatto ◴[] No.44390046{3}[source]
Not if you use the managed services which is a very alluring proposition for most businesses.