Lessons Learned from Converting a Web Application to Multitenancy and Deploying it to Amazon Web Services using Scalarium

Lessons Learned from Converting a Web Applicationto Multitenancy and Deploying it to Amazon Web Services using Scalarium AWS Tech Summit for Developers and Architects Berlin, 2011-05-16

Thomas Witt@thomas_witt http://twitter.com/thomas_witt

Since 1997 … Director Product & Business Development http://www.infopark.de/

Great Websites run Infopark Founded in 1994 in Berlin CMS, CRM and Online Marketing Software Large Websites for Enterprises

References http://www.infopark.de/references

References infopark.de/references http://www.infopark.de/references

What are we going to learn … Why did Infopark move to «The Cloud»™? How did we do it? What did we learn from it?

Why?(You will be cloudiﬁed. Resistance is futile.)

Enterprise Software Installation sucks.

http://www.alexa.com/siteinfo/cortalconsors.de

http://www.alexa.com/siteinfo/bundestag.de

http://www.alexa.com/siteinfo/munich-airport.de

Modern Web-Siteshave to be cloud based.

Our partner http://aws.amazon.com/

Multitenancy (Yes, we scale!)

“Multitenancy refers to a principlein software architecture where asingle instance of the softwareruns on a server, serving multipleclient organizations (tenants). http://en.wikipedia.org/wiki/Multitenancy

Enabling MultitenancyCreate a "shared nothing"architectureMove all conﬁguration intothe databaseExtract background tasksChoose database tenantwise

Implementing DB switching is easytenant = request.host.split(.).firstbegin @@db ||= CouchRest.database(tenant)rescue raise "tenant name #{tenant} doesnt exist"end

System Architecture Fiona on SaaS SaaS Cluster Scalarium SES: E-Mail AZ 1 AZ 2 AZ 3 EC2: EC2: EC2: EC2: EC2: EC2: S3: DB Fiona, OMC, Fiona, OMC, Fiona, OMC, Fiona, OMC, Fiona, OMC, Fiona, OMC, Assets Backup DB, Search DB, Search DB, Search DB, Search DB, Search DB, Search (Blobs) Server Redis/ Elastic Load Balancing: *.saas.infopark.net Resque Customer AZ 1 AZ 2 EC2: EC2: GitHub S3 Rails, Rails, DB Replica DB Replica + Hoptoad Cloud Front Elastic Load Balancing: CDN customer.com New Relic

Use multipleAvailability Zones!http://broadcast.oreilly.com/2011/04/the-aws-outage-the-clouds-shining-moment.html

Database (Choose wisely)

Problems with SQL databases in the cloud Bottleneck Doesn‘t scale Single point of failure Adding new Replicas Consistent backups Recovery times after crashes

SQL databases are not built for the cloud.

NoSQL databases ARE built for the cloud.… by trading off consistency for partition tolerance http://en.wikipedia.org/wiki/CAP_theorem

Database backendAdvantages Simple handling Better replication Stability and reliability SchemalessLots of ﬂavours CouchDB/BigCouch, SimpleDB, MongoDB, …We have chosen BigCouch. http://couchdb.apache.org/

Automatize! (Scalarium is your friend)

Your server – à la carte http://www.opscode.com/chef/

Auto Healing (and scaling)

Automatize using ScalariumAutomated Machine Installs No hassle with AMI Images Always install from scratch Using Chef RecipesMonitoring and Scaling Auto Healing Time Based Scaling Load Based Scaling http://www.scalarium.com/

Security(… theres lots of interesting data in the cloud)

Have multiple AWS accounts https://aws-portal.amazon.com/gp/aws/developer/account/

Use MFA Devices http://aws.amazon.com/mfa/

Security is important! Have multiple AWS accounts Use IAM • Rotate your keys • Use an MFA Device • Lock up your master account Clear concept how to handle policies, accounts, groups Have lots of Account/Key Pairs with restricted access Automatize everything • Security Groups • Regular Firewall checks • Account creation / deletion

People(The Human Factor)

“I dont «own» my data anymore.

“What about data privacy?

“Is your security good enough? How can I trust you?

“My job went to SaaS!

Have good answersto these questions. (Try to rationalize the discussion)

Disadvantages? What‘s missing?

Disadvantages? What‘s missing?Amazon Automated creation of multiple accounts with separate billing API for BillingScalarium Access Rights Security Groups MFA Support

Conclusion Have a scalable multitenancy architecture Automatize everything Don‘t forget The Human Factor

Thats a wrap! Twitter: @infopark facebook.com/infopark Thank you! Thomas Witt Director Product & Business Development thomas.witt@infopark.de +49-151-140690-23 Twitter: @thomas_witt Infopark AG • Kitzingstraße 15 • D-12277 Berlin • www.infopark.de • info@infopark.de

http://lanyrd.com	62
http://www.thomas-witt.com	6
http://twitter.com	1
https://lanyrd.com	1
http://www.linkedin.com	1

Lessons Learned from Converting a Web Application to Multitenancy and Deploying it to Amazon Web Services using Scalarium

by Thomas Witt on May 16, 2011

Accessibility

Categories

Upload Details

Usage Rights

5 Embeds 71

Statistics

Lessons Learned from Converting a Web Application to Multitenancy and Deploying it to Amazon Web Services using Scalarium Presentation Transcript