David Rosenthal: evaluation

Transcript context

…They're getting better deals on their servers, so they're passing those along to you. Yup. (3) You don't have to guess on infrastructure capacity ahead of time. AWS is elastic. As you need more, it scales up. As you need less, it scales down. And that’s actually, (4) It can scale down. When projects don't work, you're not stuck with legacy leftover infrastructure from things that don't work. (5) Engineers can focus on writing code, not installing infrastructure. Focus on what makes your beer taste better. And then, (6) You're instantly global on AWS, versus when you run your own on-prem datacenters, you're like, wherever your data centers are. Which sounds nice. It's not quite true. It's not one global availability zone. Actually, interesting point, that was the original premise. They thought they were going to abstract that away, and you were going to imagine a global S3 data center. When you deployed it, it just went to all of the datacenters, and then they quickly realized, we're going to have so much traffic from so many customers that we're going to consume WAN. We're going to consume the Internet's bandwidth replicating unnecessarily. There is, you do not run globally by default in every single. Anyway, yes. There's this step two, which is building in the cloud. That's taking advantage of using things like the relational database service, that RDS, the very early thing that they launched, which is, hey, this isn't just your exact same code and your exact same infrastructure, but in our data center and build differently, you're actually taking advantage of a cloud-native service. Then there's building for the cloud, and that's the future. Those are things like Lambda and DynamoDB. If you think about Lamda, for folks who have not done this or heard of the serverless movement, it's this idea that you don't even need to reserve an EC2 instance or deploy code to it. You just write your code and then when you want to call it, a thing just spins up for a few milliseconds, runs your code, and spins down. You were never aware of its IP address or where in the world it was. You just know that your code executed. That's really like building for the cloud. You're completely architecting your application differently to take advantage of this very different world of computing the cloud offers.…

Stored transcript either side of the excerpt. The highlighted words are the published quote; the surrounding text is unedited source, never generated.