AWS OpsWorks 与 AWS Beanstalk 与 AWS CloudFormation? [英] AWS OpsWorks vs AWS Beanstalk vs AWS CloudFormation?
问题描述
我想知道使用 AWS OpsWorks 与 AWS Beanstalk 和 AWS CloudFormation 的优缺点是什么?
我对一个可以自动扩展以处理任何大量并发 Web 请求(从每分钟 1000 个请求到 1000 万转)的系统感兴趣，其中包括一个可以自动扩展的数据库层.
理想情况下，我希望有效地共享一些硬件资源，而不是为每个应用程序设置一个单独的实例.过去我主要使用 EC2 实例 + RDS + Cloudfront + S3
堆栈系统将托管一些我们从 Heroku 迁移的高流量 ruby on rails 应用程序，还有一些 python/django 应用程序和一些 PHP 应用程序.
提前致谢.
我想知道使用 AWS OpsWorks 与 AWS Beanstalk 和 AWS CLoudFormation 的优缺点是什么?
答案是:视情况而定.
AWS OpsWorks 和 AWS Beanstalk(有人告诉我)只是管理基础设施的不同方式，这取决于您的想法.CloudFormation 只是一种模板化基础架构的方式.
就我个人而言，我更熟悉 Elastic Beanstalk，但对每个人都有自己的了解.我更喜欢它，因为它可以通过 Git 进行部署.Elastic Beanstalk 在幕后使用 CloudFormation 来启动其环境是公开信息.
对于我的项目，我同时使用两者.我使用 CloudFormation 构建自定义配置的 VPC 环境、S3 存储桶和用于我的应用程序的 DynamoDB 表.然后，我在自定义 VPC 内启动了一个 Elastic Beanstalk 环境，该环境知道如何与 S3/DynamoDB 资源对话.
<块引用>我对一个可以自动扩展以处理任何大量并发 Web 请求(从每分钟 1000 个请求到 1000 万转)的系统感兴趣，其中包括一个可以自动扩展的数据库层.
在幕后，OpsWorks 和 Elastic Beanstalk 使用 EC2 + CloudWatch + Auto Scaling，它能够处理您所说的负载.RDS 支持可扩展的基于 SQL 的数据库.
<块引用>理想情况下，我希望有效地共享一些硬件资源，而不是为每个应用程序设置一个单独的实例.过去我主要使用 EC2 实例 + RDS + Cloudfront + S3
根据一些硬件资源"的含义，您始终可以在 OpsWorks 或 Elastic Beanstalk 环境旁边启动独立的 EC2 实例.目前，Elastic Beanstalk 支持每个环境一个 webapp.我不记得 OpsWorks 支持什么.
<块引用>堆栈系统将托管一些我们从 Heroku 迁移的高流量 ruby on rails 应用程序，还有一些 python/django 应用程序和一些 PHP 应用程序.
AWS 完全支持所有这些.OpsWorks 和 Elastic Beanstalk 已经针对一系列开发环境进行了优化(Ruby、Python 和 PHP 都在列表中)，而 EC2 提供了原始服务器，您可以在其中安装任何您想要的东西.>
I would like to know what are the advantages and disadvantages of using AWS OpsWorks vs AWS Beanstalk and AWS CloudFormation?
I am interested in a system that can be auto scaled to handle any high number of simultaneous web requests (From 1000 requests per minute to 10 million rpm.), including a database layer that can be auto scalable as well.
Instead of having a separate instance for each app, Ideally I would like to share some hardware resources efficiently. In the past I have used mostly an EC2 instance + RDS + Cloudfront + S3
The stack system will host some high traffic ruby on rails apps that we are migrating from Heroku, also some python/django apps and some PHP apps as well.
Thanks in advance.
I would like to know what are the advantages and disadvantages of using AWS OpsWorks vs AWS Beanstalk and AWS CLoudFormation?
The answer is: it depends.
AWS OpsWorks and AWS Beanstalk are (I've been told) simply different ways of managing your infrastructure, depending on how you think about it. CloudFormation is simply a way of templatizing your infrastructure.
Personally, I'm more familiar with Elastic Beanstalk, but to each their own. I prefer it because it can do deployments via Git. It is public information that Elastic Beanstalk uses CloudFormation under the hood to launch its environments.
For my projects, I use both in tandem. I use CloudFormation to construct a custom-configured VPC environment, S3 buckets and DynamoDB tables that I use for my app. Then I launch an Elastic Beanstalk environment inside of the custom VPC which knows how to speak to the S3/DynamoDB resources.
I am interested in a system that can be auto scaled to handle any high number of simultaneous web requests (From 1000 requests per minute to 10 million rpm.), including a database layer that can be auto scalable as well.
Under the hood, OpsWorks and Elastic Beanstalk use EC2 + CloudWatch + Auto Scaling, which is capable of handling the loads you're talking about. RDS provides support for scalable SQL-based databases.
Instead of having a separate instance for each app, Ideally I would like to share some hardware resources efficiently. In the past I have used mostly an EC2 instance + RDS + Cloudfront + S3
Depending on what you mean by "some hardware resources", you can always launch standalone EC2 instances alongside OpsWorks or Elastic Beanstalk environments. At present, Elastic Beanstalk supports one webapp per environment. I don't recall what OpsWorks supports.
The stack system will host some high traffic ruby on rails apps that we are migrating from Heroku, also some python/django apps and some PHP apps as well.
All of this is fully supported by AWS. OpsWorks and Elastic Beanstalk have optimized themselves for an array of development environments (Ruby, Python and PHP are all on the list), while EC2 provides raw servers where you can install anything you'd like.
这篇关于AWS OpsWorks 与 AWS Beanstalk 与 AWS CloudFormation?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
