Why should You
migrate to Amazon Web Services

Some time ago we have released an article
“Why not to migrate to AWS”
written with a hint of sarcasm.

 

Reactions and comments revealed, that our level of irony was a bit too high for some people to bare. Many of you really thought that we advice not even to think about migrating to AWS. We’ll, it’s time to reveal the truth. We are convinced that migration to the AWS cloud is the best you can do for your company in terms of infrastructure to boost up your business.

Leading thru few (anti)theses written in our last article and showing how we handle them


1. Costs are not predictable in the cloud

This statement is so not true. In AWS we can precisely establish the maximum amount of money to be paid for our instances and other services that used in AWS. All kind of billing alerts can be set to ensure that the budgets are not crossed. We also take an advantage of “pay for what you use”. This, in other words, means that if you set your infrastructure correctly then you only pay for actual utilization. In case of e-commerce for example, costs may increase only in case many customers want to make order and AWS decided (by your configuration/approval) to start more instances to support more traffic.

Starting entire development stream? What seems to be the problem? Start 50 perfectly configured servers (in almost no time) to test your theory and after it’s done just shut them down. Cost? Only for real usage = as low as possible. We had a use case when we had to test our software against 100 instances to see how it scales. We started 100 t2.nano instances for 30 minutes. Cost? 0.5USD – doesn’t seem to be a lot for dedicated infrastructure for testing, does it?…

We, the Tameshi, help companies to design the infrastructure in predictable and most efficient way to let you focus only on your business and not on AWS bills.


2. Servers have lower uptime in the cloud

In AWS we take advantage of Pets vs Cattle. What does that mean? Well… in old Data Center you worried about high uptimes of your not used application servers to take over traffic from your Black Friday (even if Black Friday is not happening within the next 6 months). In AWS we create infrastructure that is not based on your Black Friday but reacts on your customers. If we see increased traffic we SCALE OUT – add new servers. If we see that you don’t have the need to have this large amount of servers we SCALE DOWN. This means that your servers can be thrown away like cattle as you don’t care about them as you would care about your personal pets. Within a day you can have 100 reboots of your infrastructure without impacting user experience. So… why worry about high uptimes when you only should worry about the fact that your service is up & running?

We can help you design your infrastructure and application in a way that allows to use the best scaling policies possible.


3. Scaling out for your clients can be easily predicted in the cloud

This sentence is true and is so not true at the same time. It all depends on what you design in the first place. Proper policies in Auto Scaling allow to scale out only during peeks, and scaling down helps to lower your infrastructure cost in case your clients don’t need so many servers. This mean you don’t PLAN that today you will have under 10 instances. You PLAN that your service will be running independently on your or your clients activities. No need to worry about black fridays, extra newsletters or simply regular operational day. AWS does it for you, and we help you focus on your business plan and spend less time on infrastructure.


4. R&D hot heads will be able to test their ideas too fast

In order to be ahead of your competition you need to have R&D. You need to innovate and test new ideas. And what’s better to do so than AWS Cloud? We can help you quickly design new infrastructure that tests your ideas without having to pay large upfront fees. Focus on expanding your ideas and we will focus on where and how to run it in the best way. You can make use of plain EC2, Dockers or Serverless. We can show you what are the options to implement your ideas in the Cloud in the most efficient way possible.


5. Operation guys will have more sleep

In old data center model we used to be woken up in case we had a server reboot or one of our FAN-s broke down which may have lead to serious outages. In Cloud you don’t need to worry about this anymore. If you design (with our help) your infrastructure in a proper way – using Self Healing – you don’t need to focus on server reboots, scaling out or broken FANs. In fact in AWS you don’t even know that fan broke down, AWS takes care for that so you don’t have to.

We believe in shared responsibility model:

  • AWS worries about underlying infrastructure (like FANs, CPUs etc)
  • Tameshi worries about best possible configuration of your application
  • You focus on YOUR business

We can help you design best possible Disaster Recovery models in case of Service Disruption that covers EC2 failure, Availability Zone failure or even Regional Failure to ensure your services will always be online with the best possible User Experience.


6. You will have to hire expensive AWS experts

We once had a client that had 20 operational people that used to handle and monitor every bit of their infrastructure. Cost of having 20 people were quite high, the number of services that they were monitoring was around 20 (avg. 1 person per project). In the same time we started cooperation with client who was paying for AWS experts/partners. They used to have 400 applications that were designed and well maintained by 2 AWS Experts and small team (~5-10) of operational guy-s. You can do the math 🙂

We can help you design your infrastructure that will be self healing and will be self-monitored.


7. AWS Cloud is not as secure as your own Data Center

Let me cite AWS webpage:
Cloud security at AWS is the highest priority. As an AWS customer, you will benefit from a data center and network architecture built to meet the requirements of the most security-sensitive organizations. An advantage of the AWS cloud is that it allows customers to scale and innovate, while maintaining a secure environment. Customers pay only for the services they use, meaning that you can have the security you need, but without the upfront expenses, and at a lower cost than in an on-premises environment.

 

With AWS you can have all of your traffic encrypted, all your data encrypted at rest and even the hardest compliance programs fulfilled, including but not limited to: “CSA, ISO 9001, ISO 27001, ISO 27017, ISO 27018, PCI DSS Level 1, SOC 1, SOC 2, SOC 3” (for more information go to: https://aws.amazon.com/compliance/programs/)


So, if despite all of the above facts you’re still crazy enough to go to the AWS cloud as we were, irrespectively if you’re not frightened by lower initial costs, cheaper PoC infrastructure setup or autoscaling doing the magic for your e-commerce, we’ll be more than happy to give you all the support need!

 

Contact us at contact@tameshi.eu for more details.

Leave a comment