Rebate Networks Gmbh - AWS Customer Presentation
•
1 like•1,114 views
Presented at AWS Tech Summit, Berlin, May 2011
Recommended
Recommended
More Related Content
What's hot
What's hot (19)
Viewers also liked
Viewers also liked (20)
Similar to Rebate Networks Gmbh - AWS Customer Presentation
Similar to Rebate Networks Gmbh - AWS Customer Presentation (20)
More from Amazon Web Services
More from Amazon Web Services (20)
Recently uploaded
Recently uploaded (20)
Rebate Networks Gmbh - AWS Customer Presentation
- 1. Group-buying as a service in the cloud Fabienne Serrière Technical Project Manager, Rebate Networks AWS Tech Summit, 16.05.11, Kalkscheune, Berlin
- 2. A bit about Rebate Networks
- 3. Rebate Networks is a network of daily deal-platforms in 29 countries on 3 continents
- 5. Columbia
- 6. Uruguay
- 7. Austria
- 8. Germany
- 9. Switzerland
- 10. UK
- 11. China
- 12. Philippines
- 13. Thailand
- 14. Indonesia
- 15. Bulgaria
- 16. Macedonia
- 17. Croatia
- 18. Serbia
- 19. Slovenia
- 20. Romania
- 21. Malaysia
- 22. Singapore
- 23. Vietnam
- 24. Hungary
- 25. Japan
- 26. Czech Republic
- 27. Estonia
- 28. Finland
- 29. Latvia
- 30. Lithuania
- 33. 23 additional payment methods (additional to the original magento payment methods)Some Numbers from Rebate Networks
- 35. Columbia
- 36. Uruguay
- 37. Austria
- 38. Germany
- 39. Switzerland
- 40. UK
- 41. China
- 42. Philippines
- 43. Thailand
- 44. Indonesia
- 45. Bulgaria
- 46. Macedonia
- 47. Croatia
- 48. Serbia
- 49. Slovenia
- 50. Romania
- 51. Malaysia
- 52. Singapore
- 53. Vietnam
- 54. Hungary
- 55. Japan
- 56. Czech Republic
- 57. Estonia
- 58. Finland
- 59. Latvia
- 60. Lithuania
- 62. Columbia
- 63. Uruguay
- 64. Austria
- 65. Germany
- 66. Switzerland
- 67. UK
- 68. China
- 69. Philippines
- 70. Thailand
- 71. Indonesia
- 72. Bulgaria
- 73. Macedonia
- 74. Croatia
- 75. Serbia
- 76. Slovenia
- 77. Romania
- 78. Malaysia
- 79. Singapore
- 80. Vietnam
- 81. Hungary
- 82. Japan
- 83. Czech Republic
- 84. Estonia
- 85. Finland
- 86. Latvia
- 87. Lithuania
- 89. How we chose AWS We were using another cloud hosting service provider.
- 90. How we chose AWS We were using another cloud hosting service provider. We were having availability problems due to the cloud service’s instability.
- 91. How we chose AWS We were using another cloud hosting service provider. We were having availability problems due to the cloud service’s instability. Our quick fixwas to do a 1:1 migration.
- 92. How we chose AWS We were using another cloud hosting service provider. We were having availability problems due to the cloud service’s instability. Our quick fixwas to do a 1:1 migration. We migrated our first region to AWS January 16, 2011, and finished moving the last region at the beginning of April 2011.
- 93. How we chose AWS We were using another cloud hosting service provider. We were having availability problems due to the cloud service’s instability. Our quick fixwas to do a 1:1 migration. We migrated our first region to AWS January 16, 2011, and finished moving the last region at the beginning of April 2011. We went from a classical stack in the cloud, to a classical stack in AWS.
- 94. How we chose AWS We went from a classical stack in the cloud, to a classical stack in AWS.
- 96. Didn‘t think much before leaping (desperate for uptime)
- 105. Cloudfront: performing well, less pricey than Akamai
- 108. Cloudfront: performing well, less pricey than Akamai
- 109. System latency: Good for our needs
- 110. System stability: Awesome uptime
- 111. Main features are doing what we expected
- 113. Hidden limitations of AWS:
- 117. Hidden limitations of AWS:
- 119. Hidden limitations of AWS:
- 120. Not able to use only Simple Email Service, attachments via Postfix
- 122. Hidden limitations of AWS:
- 123. Not able to use only Simple Email Service, attachments via Postfix
- 124. Multiregion connecting to an RDS instance from one AWS region (US West to EU West) is not possible, so it’s not possible to backup databases: administration of AWS is per AWS region
- 125. Loadbalancing: No backend loadbalancing (e.g. db), setting up ssl certs on loadbalancers is not straightforward, configuration of loadbalancers is very simplistic
Editor's Notes
- ----- Meeting Notes (5/13/11 13:28) ------ each region is separate aws account because we aren't using iam ("eye-m")- four regions in EU, 1 in South America-
- EBL ReadLatency: Time taken between a request and the corresponding response as seen by the LoadBalancer.RDS ReadLatency: The average amount of time taken per disk I/O operation.