简体繁体 English

带有负载均衡器的AWS Magento

[英]AWS Magento with Load Balancer

原文 2015-04-12 11:51:49 1 1 php/ magento/ amazon-web-services/ amazon-ec2/ amazon-s3

I plan to use Amazon EC2 Server(s) for Magento. 我计划对Magento使用Amazon EC2服务器。 But I'm fairly new to AWS. 但是我对AWS还是很陌生。

I know that I have to use Elastic Load Balancer (ELB) to balance load between two or more EC2-Instances. 我知道我必须使用弹性负载平衡器（ELB）来平衡两个或更多EC2实例之间的负载。 - That is important, because it's highly possible, that my main instance is having a loading peek 1-2 hours per day. -这很重要，因为很有可能我的主要实例每天要进行1-2个小时的偷看。

I can`t connect one EBS to two EC2-Instances, I know. 我知道我无法将一个EBS连接到两个EC2实例。 But I have to have the very same data on both (or more) EC2-Instances. 但是我必须在两个（或多个）EC2-实例上具有完全相同的数据。 - One possible solution is to make a snapshot of Instance-1 and start it to Instance-2. -一种可能的解决方案是制作Instance-1的快照并将其启动到Instance-2。 But as the data can change really quickly (Cache for example, new products ...) it's maybe not the best solution, I think. 但是，我认为，由于数据可以非常快速地更改（例如，缓存，新产品等），因此它可能不是最佳解决方案。

I heard that I can mount my S3-Storage to my instances and then use this as "global" storage, but as far as I know from different articles S3 is not quickly enough for a high-peek-storage-server. 我听说我可以将S3-Storage挂载到实例上，然后将其用作“全局”存储，但是据其他文章所知，S3对于高配置存储服务器来说还不够快。

Some facts by the way: this server is going to have 200-300 visitors per hour, but it can be 500-1000 too. 顺便说一句事实：该服务器每小时将有200-300位访客，但也可能是500-1000位访客。

Conclusion: I need a Storage Server, that is quick enough to share a lot of data (images, js, css, php) and is mountable to more than one instance. 结论：我需要一台存储服务器，它必须足够快地共享大量数据（图像，js，css，php），并且可以安装到多个实例上。 How do I do this in a clever way? 我如何聪明地做到这一点？

Greetings Bubble 问候泡泡

1 个解决方案

The new EFS service (NFS share) can give you a simple solution to what you are seeking to do, but its cost is high compared to the alternatives. 新的EFS服务（NFS共享）可以为您要执行的操作提供简单的解决方案，但是与其他选择相比，它的成本很高。

When you are dealing with multiple instances your instances should follow the shared nothing architecture. 当您处理多个实例时，您的实例应遵循“无共享”架构。 Meaning, any unique application data is not stored on the instance. 这意味着，任何唯一的应用程序数据都不会存储在实例上。

Application code can be stored on the instance, you should have a release process to update this automatically on an instance if its changed. 应用程序代码可以存储在实例上，如果实例发生更改，您应该具有一个释放过程以在实例上自动对其进行更新。

Cache data is something that can be regenerated, this ideally should be a memory cache like memcached. 缓存数据是可以重新生成的，理想情况下，它应该是像memcached这样的内存缓存。

Application data (Product images, etc) should be stored on S3. 应用程序数据（产品图像等）应存储在S3上。 You can also serve from S3 (which offloads some of the work from your web server). 您也可以从S3提供服务（这会减轻Web服务器的工作量）。 I believe there are plugins for Magento to store images on s3. 我相信有Magento的插件可以在s3上存储图像。

Database should be on a server outside of web server instance. 数据库应位于Web服务器实例之外的服务器上。 You may be able to use RDS to set this up quickly. 您可能可以使用RDS进行快速设置。