The following presentation was created by Dr. Matt Wood, Senior Manager at Amazon Web Services (AWS). It contains relevant information for those considering using Amazon Web Services to build high performance web applications. You will learn about the main building blocks (storage, compute, databases, managed services) for great applications and how to use AWS to support you along the way.
Its a common believe that Cloud is good for green field apps. There are many reasons for this, in particular the fact that the cloud forces a different kind of thinking on how to run apps. Native cloud apps were designed to scale elastically, they were designed with complete automation in mind, and so forth.
Amazon offers a cloud-based relational database service called RDS. The first type of database available via RDS was MySQL. Now Amazon RDS also supports Microsoft SQL Server express, web, standard, and enterprise, as well as Oracle standard and enterprise editions.
This article contains information on how to set up MySQL Community and then connect to a MySQL RDS instance with phpmyadmin. If you are just starting with Amazon cloud, note that recently Amazon announced its release of a free tier for RDS.
AWS cloud products facilitate the way you can easily and in a reasonable time, deploy a scalable online service on Amazon cloud infrastructure. The slides include schemes that deal with the different cloud aspects such as elasticity, performance and security. The architectures demonstrated uses some advanced AWS products such as Auto-scaling, RDS, Route53 and much more. The presentation is a bit long, take your time and you will find these AWS features that can help you understand how to get more of your AWS cloud account.
Currently IT departments and infrastructure providers are under increasing pressure to provide computing infrastructure at the lowest possible cost. Evolution of the Cloud computing paradigm has made software systems more scalable with a cost-effective approach. One of the most popular and innovative Cloud infrastructure providers is Amazon Cloud Services (AWS).
WordPress is one of the most popular open source blog platforms out there. It is used to power anything from simple blogs to complex portals, thanks to the variety of plugins the community has developed.
In this article we will describe the architecture options for deploying WordPress in AWS with scalability and high availability in mind. We will take advantage of the elasticity of the cloud and use more servers when we need them and less when we don’t (auto-scaling).
After tracking more than $200,000,000 in AWS EC2 spend, Newvem has identified that more than 35% of its users operate an AWS cloud that is highly vulnerable to outages. Many cases were identified in which users had improperly configured Elastic Load Balancers (ELBs) and as much as 40% of users’ cloud data wasn’t backed up. High availability when deploying applications is crucial. This article will explain how Newvem analyzes your availability levels but first let’s talk about best practices when deploying applications in the cloud.
Following Max B. post on KnowYourCloud and based on questions received at AWS Usergroup meetups I realized that there is a reasonable (but sometimes exaggerated) concern about the level of lock-in to AWS. In this article we will try to put the problem in the right perspective and explain the practical lock-in considerations for the various services of Amazon’s cloud.
What is vendor lock-in? Vendor lock-in is the situation where a business becomes overly dependent on a specific service or product provider.
Should I worry?
