Evolution of 'Undifferentiated Heavy Lifting'

It all started with Iaas Providers doing the undifferentiated heavy lifting required for performing mundane activities like spinning up new server instances (Compute), Storage and Networks. Paas provided the deployment and development environments. Thus businesses can focus on their core areas and are not held back by IT/Operations in bringing a new idea quickly to the market. EC2, S3 in AWS or OpenStack Nova, Neutron and Swift can be viewed as 1st Generation of Heavy Lifting.

Next came the concept of Lambda function and we have Serverless, where we can 'pay for value' and AWS Lambda metering done in increments of 100 milliseconds. We have AWS Fargate for running Containers without bothering about servers. Similarly Serverless DBs for Aurora and DynamoDB and even Serverless Orchestration using AWS Step Functions. We can view these as 2nd Generation of Heavy Lifting.

Services like 'AWS Deep Learning Containers', where containers come with pre-installed Docker images are the next generation of Heavy Lifting.They come with deep learning frameworks and simplify deployment of custom Machine Learning (ML) environments. Also with services like 'CodeCommit', 'CodeBuild', 'CodePipeline', 'CodeDeploy', 'CodeStar' and Cloud based IDE like Cloud9, even the development, build and release engineering is heavy lifted. Though these are similar to other Paas providers, but the way they are integrated with different AWS services and charging only for the resources used like EC2 is taking all this to a new level.

Now with all this amount of undifferentiated heavy lifting of Serverless clubbed with Codeless Automation testing, there's nothing holding us back from bringing an idea quickly to market. We are only limited by the number of creative use-cases we can come up with and convert them to business hypotheses. And with these lower and lower barriers of entry, complemented by cheaper broad-band, the world of computing is truly democratic more than ever.

要查看或添加评论,请登录

Phani Kiran R的更多文章

  • DevOps - Idle Time

    DevOps - Idle Time

    When we talk about DevOps, we often hear references to lead time and cycle time. In this post, I want to focus on idle…

  • Downstream Optimization - Make Work Flow Better

    Downstream Optimization - Make Work Flow Better

    It is almost year-end and festivities are around the corner. ServiceNow IDC gifted one of the best-selling books - “The…

    1 条评论
  • Evolutionary Processes Vs Revolutionary Tools

    Evolutionary Processes Vs Revolutionary Tools

    Reading this article titled, "A Fool With A Tool Is Still A Fool" inspired me to post below thoughts and observations:…

    1 条评论
  • Invest In Your User Stories

    Invest In Your User Stories

    Recently i came across an acronym/criteria that can be used to verify if Agile User Stories are ready for the…

  • WIP - Work In Progress or Waste In Progress ?

    WIP - Work In Progress or Waste In Progress ?

    Concept of limiting WIP (Work In Progress) in DevOps is inspired from the manufacturing world. From the Toyota…

    1 条评论
  • DevOps - Automation

    DevOps - Automation

    In continuation of my previous article on DevOps Culture, i would like to touch upon 'Automation', the 'A' in the CAMS…

    2 条评论
  • DevOps & Its Contradictions

    DevOps & Its Contradictions

    CAMS Model, coined by Damon Edwards and John Willis is a good way to understand DevOps. CAMS stands for Culture…

  • Ceremonious Agile

    Ceremonious Agile

    Reading this article on 'Fake Agile' made me pen my thoughts as below: Whether you call it Agile or SRE or DevOps or…

    2 条评论
  • DevOps - Culture

    DevOps - Culture

    A recent training I attended on DevOps is the genesis for this post. The trainer focused on throwing names of different…

  • Ideal Service Assurance COTS ?

    Ideal Service Assurance COTS ?

    After spending more than a decade working with industry leading Service Assurance (Fault/Performance/Service…

    3 条评论

社区洞察

其他会员也浏览了