Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Rebate Networks Gmbh - AWS Customer Presentation

1,559 views

Published on

Presented at AWS Tech Summit, Berlin, May 2011

Published in: Technology, Business
  • Be the first to comment

Rebate Networks Gmbh - AWS Customer Presentation

  1. 1. Group-buying as a service in the cloud<br />Fabienne Serrière<br />Technical Project Manager, Rebate Networks<br />AWS Tech Summit, 16.05.11, Kalkscheune, Berlin<br />
  2. 2. A bit about Rebate Networks<br />
  3. 3. Rebate Networks is a network of daily deal-platforms in 29 countries on 3 continents <br />
  4. 4. Rebate Networks countries<br />Americas<br />Europe<br />Asia<br /><ul><li>Argentina
  5. 5. Columbia
  6. 6. Uruguay
  7. 7. Austria
  8. 8. Germany
  9. 9. Switzerland
  10. 10. UK
  11. 11. China
  12. 12. Philippines
  13. 13. Thailand
  14. 14. Indonesia
  15. 15. Bulgaria
  16. 16. Macedonia
  17. 17. Croatia
  18. 18. Serbia
  19. 19. Slovenia
  20. 20. Romania
  21. 21. Malaysia
  22. 22. Singapore
  23. 23. Vietnam
  24. 24. Hungary
  25. 25. Japan
  26. 26. Czech Republic
  27. 27. Estonia
  28. 28. Finland
  29. 29. Latvia
  30. 30. Lithuania
  31. 31. Ukraine</li></li></ul><li>Some Numbers from Rebate Networks<br />
  32. 32. <ul><li>12 Countries with 16 Languages
  33. 33. 23 additional payment methods (additional to the original magento payment methods)</li></ul>Some Numbers from Rebate Networks<br />
  34. 34. Rebate Networks countries<br />Americas<br />Europe<br />Asia<br /><ul><li>Argentina
  35. 35. Columbia
  36. 36. Uruguay
  37. 37. Austria
  38. 38. Germany
  39. 39. Switzerland
  40. 40. UK
  41. 41. China
  42. 42. Philippines
  43. 43. Thailand
  44. 44. Indonesia
  45. 45. Bulgaria
  46. 46. Macedonia
  47. 47. Croatia
  48. 48. Serbia
  49. 49. Slovenia
  50. 50. Romania
  51. 51. Malaysia
  52. 52. Singapore
  53. 53. Vietnam
  54. 54. Hungary
  55. 55. Japan
  56. 56. Czech Republic
  57. 57. Estonia
  58. 58. Finland
  59. 59. Latvia
  60. 60. Lithuania
  61. 61. Ukraine</li></li></ul><li>Rebate Networks countries hosted on AWS<br />Americas<br />Europe<br />Asia<br /><ul><li>Argentina
  62. 62. Columbia
  63. 63. Uruguay
  64. 64. Austria
  65. 65. Germany
  66. 66. Switzerland
  67. 67. UK
  68. 68. China
  69. 69. Philippines
  70. 70. Thailand
  71. 71. Indonesia
  72. 72. Bulgaria
  73. 73. Macedonia
  74. 74. Croatia
  75. 75. Serbia
  76. 76. Slovenia
  77. 77. Romania
  78. 78. Malaysia
  79. 79. Singapore
  80. 80. Vietnam
  81. 81. Hungary
  82. 82. Japan
  83. 83. Czech Republic
  84. 84. Estonia
  85. 85. Finland
  86. 86. Latvia
  87. 87. Lithuania
  88. 88. Ukraine</li></li></ul><li>How we chose AWS<br />
  89. 89. How we chose AWS<br />We were using another cloud hosting service provider.<br />
  90. 90. How we chose AWS<br />We were using another cloud hosting service provider.<br />We were having availability problems due to the cloud service’s instability.<br />
  91. 91. How we chose AWS<br />We were using another cloud hosting service provider.<br />We were having availability problems due to the cloud service’s instability.<br />Our quick fixwas to do a 1:1 migration.<br />
  92. 92. How we chose AWS<br />We were using another cloud hosting service provider.<br />We were having availability problems due to the cloud service’s instability.<br />Our quick fixwas to do a 1:1 migration.<br />We migrated our first region to AWS January 16, 2011, and finished moving the last region at the beginning of April 2011.<br />
  93. 93. How we chose AWS<br />We were using another cloud hosting service provider.<br />We were having availability problems due to the cloud service’s instability.<br />Our quick fixwas to do a 1:1 migration.<br />We migrated our first region to AWS January 16, 2011, and finished moving the last region at the beginning of April 2011.<br />We went from a classical stack in the cloud, to a classical stack in AWS.<br />
  94. 94. How we chose AWS<br />We went from a classical stack in the cloud, to a classical stack in AWS.<br />
  95. 95. How we chose AWS<br />We went from a classical stack in the cloud, to a classical stack in AWS.<br /><ul><li>Not optimal (no architectural planning before migration)
  96. 96. Didn‘t think much before leaping (desperate for uptime)
  97. 97. Didn’t use autoscaling (because of instability problems, this was out of scope)</li></li></ul><li>Where we are now<br />
  98. 98.
  99. 99.
  100. 100. Where we are now<br /><ul><li>What is going right
  101. 101. Cloudfront: performing well, less pricey than Akamai </li></li></ul><li>Cloudfront endpoints and Rebate Networks’ countries<br />
  102. 102. via http://cedexis.com/data/charts.html<br />
  103. 103. Where we are now<br /><ul><li>What is going right
  104. 104. Cloudfront: performing well, less pricey than Akamai </li></li></ul><li>Where we are now<br /><ul><li>What is going right
  105. 105. Cloudfront: performing well, less pricey than Akamai
  106. 106. System latency: Good for our needs </li></li></ul><li>
  107. 107. Where we are now<br /><ul><li>What is going right
  108. 108. Cloudfront: performing well, less pricey than Akamai
  109. 109. System latency: Good for our needs
  110. 110. System stability: Awesome uptime
  111. 111. Main features are doing what we expected
  112. 112. Support from Amazon: billing/workshops/trainings</li></li></ul><li>Where we are now<br /><ul><li>What we are missing
  113. 113. Hidden limitations of AWS:
  114. 114. Not able to use only Simple Email Service, attachments via Postfix</li></li></ul><li>
  115. 115.
  116. 116. Where we are now<br /><ul><li>What we are missing
  117. 117. Hidden limitations of AWS:
  118. 118. Not able to use only Simple Email Service, attachments via Postfix</li></li></ul><li>Where we are now<br /><ul><li>What we are missing
  119. 119. Hidden limitations of AWS:
  120. 120. Not able to use only Simple Email Service, attachments via Postfix
  121. 121. 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</li></li></ul><li>Where we are now<br /><ul><li>What we are missing
  122. 122. Hidden limitations of AWS:
  123. 123. Not able to use only Simple Email Service, attachments via Postfix
  124. 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. 125. Loadbalancing: No backend loadbalancing (e.g. db), setting up ssl certs on loadbalancers is not straightforward, configuration of loadbalancers is very simplistic
  126. 126. No possibility to set elastic ip address to a loadbalancer (for setup of DNS A-records)</li></li></ul><li>Thank you for your attention<br />Fabienne Serrière<br />Technical Project Manager, Rebate Networks<br />fabienne.serriere@rebatenetworks.com<br />

×