3 ms·
> Amazon itself used to be that environment. Before AWS was adopted internally, which it wasn't for some time, to say nothing of the many years before it was cr
by rualca 6y ago
> Amazon itself used to be that environment. Before AWS was adopted internally, which it wasn't for some time, to say nothing of the many years before it was created, getting capacity involved a weeks or even months long political game with the infrastructure team.
It's my understanding that you're describing how Amazon worked in the 90s. It's my understanding that Amazon afterwards moved to an internal cloud provider, and afterwards spun off AWS which worked in parallel with Amazon's internal cloud provider.
- busterarm 6y ago> It's my understanding that you're describing how Amazon worked in the 90s. It's my understanding that Amazon afterwards moved to an internal cloud provider, and afterwards spun off AWS which worked in parallel with Amazon's internal cloud provider. Not at all. Amazon's transformation took years. Up until last year, amazon.com was Oracle's biggest customer. AWS development far outpaced their actual use of it.
- User23 6y agoThe website platform itself started migrating to AWS, in a crude but reasonably effective way, in 2009. Various other service owners migrated sooner though. Also there had already long been a directive to build services as though they were going to be used by external customers since the early 2000s. It's not wrong to view AWS as just another step in Amazon's long services journey, although that elides many significant events.