Tuesday, August 29, 2017

AWS Costing

If you ask any AWS geek , what is the biggest change they have noticed after moving On-Prem workloads to Cloud, you will mostly hear typical well known answers "better management" , "Less Operations overhead "...so on ..

One important trait which they aquire but will not acknowledge as they are not aware either is acquiring  a  "Mulah mindset" . [ for those who are wondering what mulah is, let me make it simple. mulah ~ money"]

Be an  Architect , IT manager, Developer one thing you need to be good at when working with AWS is costing. I know its hard , never had to deal with costing before so frequently  as old school style only involved painful money discussion during the budget cycle  when capital investment needs to be budgeted during initial stages of planning. 

Good part is, you don't need to have a Phd to understand costing but do need to spend some effort to get used to calculation. [ Paradigm shift is good thing]

AWS provides some good tools and lots of information to make life easier . Below are some useful links





Monday, August 28, 2017

AWS Elastic Beanstalk vs AWS CloudFormation

One question , i get in most of sessions when talking about Elastic Beanstalk is
"difference between Elastic beanstalk and CloudFormation"

I would like to keep this explanation very simple.

Use  Elastic Beanstalk when you want to deploy the application from supported developer tool and don't want to worry about provision of infrastructure prior to deployment. Elastic beanstalk framework will provision the infrastructure and deploy the code to servers.

Use CloudFormation  when you want a framework to define collection of related AWS resources and provision them in an orderly and predictable fashion


Important to Note 

AWS CloudFormation supports Elastic Beanstalk application environments as one of the AWS resource types


Detailed Information :

CloudFront 

Elastic Beanstalk









Tuesday, July 11, 2017

DIY vs AWS

Came across a very good , simple to understand comparison between AWS and DIY (Do-It Yourself)


DIY
AWS
Scale Up
Elastic Service(On-Demand/ When needed)
Assume Reliable Infrastructure
Assume Infrastructure Failure
Diverse Technical Expertise
Application Based Expertise
Application Unaware of Infrastructure
Application aware infrastructure
High Upfront Cost
Usage Based Cost
Design, Build, Operate
Limited Knowledge/ Shared Support
Showback , charge back challenging
Showback , Chargeback can be achieved by granular monitoring of usage

AWS vs Azure

Age old question .....

Check this comparison matrix

https://azure.microsoft.com/en-us/campaigns/azure-vs-aws/mapping/