Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

Infopark AG - AWS Customer Presentation

4.400 visualizaciones

Publicado el

Presentation on how Infopark AG uses AWS. AWS Tech Summit, Berlin, May 2011

Publicado en: Tecnología
  • Sé el primero en comentar

Infopark AG - AWS Customer Presentation

  1. 1. 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
  2. 2. Thomas Witt@thomas_witt
  3. 3. Since 1997 … Director Product & Business Development
  4. 4. Great Websites run Infopark Founded in 1994 in Berlin CMS, CRM and Online Marketing Software Large Websites for Enterprises
  5. 5. References
  6. 6. References
  7. 7. What are we going to learn … Why did Infopark move to «The Cloud»™? How did we do it? What did we learn from it?
  8. 8. Why?(You will be cloudified. Resistance is futile.)
  9. 9. Enterprise Software Installation sucks.
  10. 10.
  11. 11.
  12. 12.
  13. 13. Modern Web-Siteshave to be cloud based.
  14. 14. Our partner
  15. 15. Multitenancy (Yes, we scale!)
  16. 16. “Multitenancy refers to a principlein software architecture where asingle instance of the softwareruns on a server, serving multipleclient organizations (tenants).
  17. 17. Enabling MultitenancyCreate a "shared nothing"architectureMove all configuration intothe databaseExtract background tasksChoose database tenantwise
  18. 18. Implementing DB switching is easytenant = @@db ||= CouchRest.database(tenant)rescue raise "tenant name #{tenant} doesnt exist"end
  19. 19. 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: * Resque Customer AZ 1 AZ 2 EC2: EC2: GitHub S3 Rails, Rails, DB Replica DB Replica + Hoptoad Cloud Front Elastic Load Balancing: CDN New Relic
  20. 20. Use multipleAvailability Zones!
  21. 21. Database (Choose wisely)
  22. 22. Problems with SQL databases in the cloud Bottleneck Doesn‘t scale Single point of failure Adding new Replicas Consistent backups Recovery times after crashes
  23. 23. SQL databases are not built for the cloud.
  24. 24. NoSQL databases ARE built for the cloud.… by trading off consistency for partition tolerance
  25. 25. Database backendAdvantages Simple handling Better replication Stability and reliability SchemalessLots of flavours CouchDB/BigCouch, SimpleDB, MongoDB, …We have chosen BigCouch.
  26. 26. Automatize! (Scalarium is your friend)
  27. 27. Your server – à la carte
  28. 28. Auto Healing (and scaling)
  29. 29. 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
  30. 30. Security(… theres lots of interesting data in the cloud)
  31. 31. Have multiple AWS accounts
  32. 32. IAM
  33. 33. Use MFA Devices
  34. 34. 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
  35. 35. People(The Human Factor)
  36. 36. “I dont «own» my data anymore.
  37. 37. “What about data privacy?
  38. 38. “Is your security good enough? How can I trust you?
  39. 39. “My job went to SaaS!
  40. 40. Have good answersto these questions. (Try to rationalize the discussion)
  41. 41. Disadvantages? What‘s missing?
  42. 42. Disadvantages? What‘s missing?Amazon Automated creation of multiple accounts with separate billing API for BillingScalarium Access Rights Security Groups MFA Support
  43. 43. Conclusion Have a scalable multitenancy architecture Automatize everything Don‘t forget The Human Factor
  44. 44. Thats a wrap! Twitter: @infopark Thank you! Thomas Witt Director Product & Business Development +49-151-140690-23 Twitter: @thomas_witt Infopark AG • Kitzingstraße 15 • D-12277 Berlin • •