2015 Drupal中国营提议:Auto-Scaling Drupal as Web BaaS

drupal generates a considerable load on the web server and can quickly become resource constrained there, having multiple web servers also increases the the redundancy of your deployment. it is always a system engineering perspective to take care the platform of drupal, i have seen a site with minimum memory to be ran is 4G, at the same time it is still slow. Handling the platform well that delivering your web service could enhance end-user experience, and at the same time saving costs.

AWS provided auto-scaling, which is what we made use to launch Drupal as a distributed site. The whole distributing infrastructure is being version controlled by AWS Cloudformation's Infrastructure as code. With DevOps tools like Chef, we can pre-load every web node by configuring all of them as new nodes but not a direct restoration of a set of EC2-AMI. Which this helps the modification of code(i wonder all the time how does ppl update code when auto-scaling thru AMI, backup all the time? Thats lame.)

Why web BaaS ? cloud service exists because of charges on demand from service perspective, and layer separation to let developers to care less that they are not suppose to manage. As a system engineer, i will recommend everyone to put their web site into autoscaling architecture to cater all hazel that created by the platform. What next? more separation! Drupal should serve as a web backend, which is the view-model part in a MVVM. This could boost the performance, simplifying of frontend developers' work and anything you can imagine.

In this session we'll be discussing:
- Making use of AWS services to optimize Drupal.
- Hows does AWS services fit into Drupal
- Simple Auto-Scaling Drupal architecture
- How to use Drupal as a web backend
- And more.

Speaker Experience
- Five years of system engineering
- Current cloud system developer
- starting up with AWS expertises
- Working on a drupal product
- Supporting a 10MPV+ sites that running drupal.

Experience level:
intermediate