Symfony in the Cloud: Scaling Databases and File Uploads

Symfony in the Cloud
Kris Wallsmith

February 17, 2010

Wednesday, February 17, 2010

Kris Wallsmith
• Freelance web developer, • JavaScript (moo)
consultant, training, audits...
• @kriswallsmith
• 10 years using PHP
• CTO of Nebul.us
• 3 years using symfony
• Author of (too) many plugins
• 1 year on symfony core team


What is Nebul.us ?

• Nebul.us is a vibrant and visual life aggregator. In real time you can see
what your friends and the public are sharing and discovering online!

• Passively share what you’re doing online

• Show don’t tell


What is Nebul.us really?

• Symfony Framework

• Doctrine ORM

• Zend Framework

• Swift mailer

• and more…


What is Nebul.us really?

• Web site

• XML services (Flash and Atom)

• JSON services (browser plugins)

• Up to 12 requests per minute when browsing


Prototype


Prototype
HTTP

PHP

Local Filesystem
Sessions

Uploads
MySQL

ServerGrove VPS


What is “The Cloud”?


I don’t know.


What is “The Cloud”?

• Adds a (big) black box to your stack

• Several virtualized resources

• Scale based on the level of trafﬁc

• Pay only for what you use

• Elastic!


It’s cloudy out there

• Amazon

• Rackspace

• Microsoft

• Rightscale


Production


Production
HTTP

PHP

Local Filesystem
Sessions

Uploads
MySQL

ServerGrove VPS


No really, it’s that easy.


Writing a scalable
symfony application
Kris Wallsmith

February 17, 2010


Upgrade Points

• Database connections

• File uploads

• Session storage

• Local development

• Deploying


Database Connections



• Typical database conﬁguration



• One writable “master” connection

• One or more read-only “slave”
connections


Managing Connections

• Organize read and write connections
using a naming convention

• Choose a random read connection


Extend the Doctrine ORM

• Use the appropriate connection

• Doctrine_Query
• Doctrine_Record
• Doctrine_Collection


Conﬁgure Doctrine

• Set custom query and collection class
attributes in manager

• Set custom record class in builder
options


Using the Doctrine DBAL

• Doctrine_Manager::connection()
• $table->getConnection()


Using the Doctrine DBAL

• Doctrine_Manager::getInstance()
->getConnection('master')

• $context->getDatabaseManager()
->getDatabase('master')
->getDoctrineConnection()

• $configuration
->getWriteConnection()


How do we test this?


Connection Listener

• Listen to every connection

• Compare type of query to type of
connection


Connection Listener

• Add connection listener to debug
mode and test suite


Multiple Connections

• Conﬁgure multiple connections to the
same database


Do you want it?
Introducing sfDoctrineMasterSlavePlugin


File Uploads


File Uploads

• Typical upload form


View Layer

• Render the uploaded image


Amazon S3 Integration

• Must handle ﬁle uploads

• Must integrate with the view layer

• Must be disable-able


Stream Wrapper

• Zend Amazon S3 stream wrapper

• s3://mybucket/image.jpg


Read / write paths

• Conﬁgure read and write upload
paths


Conﬁgure Amazon S3

• Toggle integration on/off

• Environment buckets


Conﬁgure File Uploads

• Upload to the write directory

• Custom validated ﬁle class


Amazon S3 ACL

• ACL defaults to private

• Extend and change to public-read


t, ...
ss ew
Ps th
M at


View Layer

• Nothing magic

• Custom helper function that uses the
conﬁgured upload read path

• Search and replace…


Session Storage


Session Storage

• Default factories conﬁguration


Session Storage

• Store session data in the database


Database Session Storage

• Migrate the database


Local Development


Local Development

• One database

• Save uploads to the local ﬁlesystem

• Present correct upload path in view layer


Deploying


Deploying

• Subversion

• svn update

• svn checkout + symlink


Deploy with svn update

1. Disable

2. Update the working copy

3. Rebuild model ﬁles

4. Migrate the database

5. Enable


Deploy with svn checkout
1. Checkout a fresh working copy

2. Setup ﬁles not in the repository

3. Build model ﬁles

4. Disable current working copy


6. Update symlink


Deploy with svn update

1. Disable

2. Update the working copy



5. Enable


Deploy with svn checkout
1. Checkout a fresh working copy

2. Setup ﬁles not in the repository


4. Disable current working copy


6. Symlink the new working copy


Deployment Strategies

• svn update

• fewer steps

• svn checkout + symlink

• less downtime


Automated Deployment

• Rightscale API


Questions?


Symfony in the Cloud: Scaling Databases and File Uploads

Recommandé

Recommandé

Contenu connexe

En vedette

En vedette (11)

Similaire à Symfony in the Cloud: Scaling Databases and File Uploads

Similaire à Symfony in the Cloud: Scaling Databases and File Uploads (20)

Plus de Kris Wallsmith

Plus de Kris Wallsmith (15)

Dernier

Dernier (20)

Symfony in the Cloud: Scaling Databases and File Uploads