November 8th, 2010 by Arjan Olsder Posted in Analysis & Editorial | No Comments »
Last week, Glu launched their new Freemium game Gun Bros. As the company probably hoped for, the game downloads skyrocketed, but so did serverload. As a result, gamers became dissatisfied about the poor network performance.
Niccolo De Masi, CEO of Glu, did exactly what’s best in a situation like it. Confess to the consumers that the servers are a problem and note that the company is working hard on a solid solution to the problem.
“We at Glu are enthralled and appreciative of the reception you have given Gun Bros. – our first freemium-social title. We are aware of the server issues and bugs and I can assure you our teams are working tirelessly to resolve them as quickly as possible. We will restore any loss of status caused as a result of these issues as soon as possible. As a thank you for your loyalty and support, we will also include a bonus for all users in an upcoming update to the game.”
Glu is not the only publisher that has performance problems at the launch of a new freemium game. The same thing happened to ngmoco on release of their We Rule game.
Congratulations
Your first AWS Elastic Beanstalk Node.js application is now running on your own dedicated environment in the AWS Cloud
This environment is launched with Elastic Beanstalk Node.js Platform
What’s Next?
- AWS Elastic Beanstalk overview
- AWS Elastic Beanstalk concepts
- Deploy an Express Application to AWS Elastic Beanstalk
- Deploy an Express Application with Amazon ElastiCache to AWS Elastic Beanstalk
- Deploy a Geddy Application with Amazon ElastiCache to AWS Elastic Beanstalk
- Customizing and Configuring a Node.js Container
- Working with Logs
