What is the difference for a PHP application running on Amazon Elastic Beanstalk or shared instances or servers?

My question is: what is the difference for a PHP application running on Amazon Elastic Beanstalk (called EB after.) Or shared instances or servers?

I'm new to Amazon Elastic Beanstalk, I used PagodaBox.com. Is PaaS EB platform exactly the same as PagodaBox.com?

What is the difference in runtime between an application running on shared servers or an Auto-scale PaaS platform like EB?

Perhaps I will find out some. I am doing a test on both EB and PagodaBox.com, PagodaBox told me that they are the target, so you need to configure the application on the local computer, in fact they do not support the write operation from Share Dir, which is defined in Boxfile.

So is that right? and like EB, what PaaS platform will be completely different than the shared servers that host your site?

When you install a site like wordpress on a single server, you can configure and edit the file on the server side, each change will affect the source code or resource files that are part of your code. But if you use the PaaS pagoda, you cannot even perform a write operation from a shared Dir, which means you have to do everything in local and then load them as static code. all user data will be stored in the mysql database in the same way as on the shared server, but all downloads should be stored in the Shared Dir, which is defined in the Boxfile. but where should it be in EB? How do we save uploaded files if we are going to deploy a WordPress site in EB? Will it be a code change, or should we find our own way of storing resident data as we code our own application?

, EB? : , ?

, -, -. , !

+3
1

Beanstalk PaaS, , . Elastic Beanstalk , , , .

Wordpress S3 .

, Elastic Beanstalk , . .

+1

All Articles