Below it’s a summary containing stuffs from CirrusUp! Enjoy reading!
If you want to protect against sudden traffic increases, then definitely it’s a good practice to add a throttling framework. If you run your application on multiple hosts, then you need a way to synchronize statistics across entire fleet. For this use case, Redis is a perfect match.
A real-life story describing how logging ran out of control and how to increase EBS size if you run application with Elastic Beanstalk.
AWS offers a library that works as a ORM for DynamoDB. As always, there are pros and cons you should know before integrating it in your app.
Route 53 is the solution from AWS for DNS management. But comparing to other DNS solutions, it offers many fancy features like redirecting to a secondary address if the first one is not available.
Redis could be used to implement the PubSub pattern for non-critical messages. If your app can tolerate a message lost, then use Redis.
Route 53 offers a very interesting feature: behind a DNS address could be two or many services, each having different weight, the calls balancing being done by Route 53.
If you host your domain in Route 53 and want to setup email inbox, then you can choose between several solutions, but a free one is offered by Zoho.
Someone told us a story about a trivial tool that saved him during a critical event. Maybe we should learn from that story and be prepared in case this happens to us.
Looking to our traffic stats, we tend to believe you have enjoyed our topics. If you have questions or suggestions for future posts, don’t hesitate to contact us!
Happy cloud computing!