3 ms·
Its a bit deep to understand at first, but once you've been on the platform for a while, its pretty straightforward. I'm going to respectfully disagree with the
by pixeloution 13y ago
Its a bit deep to understand at first, but once you've been on the platform for a while, its pretty straightforward. I'm going to respectfully disagree with the "smaller set than people initially assume" -- there are huge differences.
Some examples:
* DNS can be set up to round robin
* auto-scaling can be built in
* load balancers are available and easy to use
* For companies with multiple employees various levels of access can be granted to the system via IAM roles
* you can add and subtract hard drives from an instance on the fly (EBS volumes)
* You can set those volumes up as RAID if you so desire.
* You can easily move IP addresses from one instance to another.
These are just the ones off the top of my head as I've been off AWS for about 6 months now. This doesn't even count how well the servers play with other amazon web services, like SQS, SNS, SES and RDS (queue, notifications, email, database).
That being said, I use DO for a few small sites I host because I don't need any of the features AWS provides.
- mgkimsal 13y agolinode has load balancing available. I'd think round robin DNS has nothing inherently to do with the infrastructure - that's a function of the DNS server, right? Yes, there are some things AWS has that other services don't. My own experiences have been that people default to thinking AWS==cloud and that's the 'best' option, and this thinking was prevalent years ago, well before SES, SQS, RDS, etc were extra reasons for integration. They've got good services, but have done a hell of a branding job over the years as well.