Issue link: https://read.uberflip.com/i/1301029
Modern compute When you're building an application, you generally have three options for compute: instances, containers, and Lambda. What you choose and how you choose it depends on how much you care about flexibility versus simplicity, because there are tradeoffs. We define "simplicity" as seamless integration with other services and features and flexibility as the ability to make more decisions about configuration. Increasingly we're seeing our customers choose containers and Lambda for compute. Containers offer excellent portability and flexibility over an application's settings. Lambda offers the most simplicity, allowing developers to focus only on the business logic of the application. Build with Serverless Simplicity Centering your application on AWS Lambda enables you to spend more time focusing on innovating your application instead of managing infrastructure. You no longer need to provision or maintain servers, operating systems, or software. This means you Modern Applications: Modern compute Serverless Compute Options AWS Lambda Serverless event-driven code execution Short-lived Data source integrations Invisible Infrastructure AWS Fargate Serverless compute engine for containers Long-running Bring existing code Fully managed orchestration can focus on writing business logic that provides differentiated value to your customers and business. Serverless technologies automatically scale by unit of work and have built-in availability and fault tolerance, so you can build customer-ready applications, right from the start. You can build serverless applications with a lower cost of ownership because you pay for execution duration, or consistent throughput, not for server unit. About containers Containers provide a standard way to package your application's code, configurations, and dependencies into a single object. Containers share an operating system installed on the server and run as resource-isolated processes, ensuring quick, reliable, and consistent deployments, regardless of environment. Containers package your code with the configuration files and dependencies it needs to consistently run in any environment. Containers also provide process isolation that lets you granularly set CPU and memory utilization for better use of compute resources.