Articles in this series

LinkedIn Twitter
Director, OpenShift Strategy at Red Hat. Founder of Rishidot Research, a research community focused on services world. His focus is on Platform Services, Infrastructure and the role of Open Source in the services era. Krish has been writing @ CloudAve from its inception and had also been part of GigaOm Pro Analyst Group. The opinions expressed here are his own and are neither representative of his employer, Red Hat, nor CloudAve, nor its sponsors.

6 responses to “Remember Next Gen PaaS and AWS? Here Is The Second Piece To The Puzzle”

  1. ankur

    The workflow component is quote a big piece of a puzzle. For instance if you want to know create a complex work flow like an order system. You only need to program up a couple of semi-dumb forms which connect to the API. You don’t need to maintain code to manage states and failovers and tons of other stuff. It is really a cool idea.

  2. Jeff Schneider

    Hey Krish –
    This is the second article I’ve read that referred to SWF as Amazon’s second step to PaaS. To be fair to AWS, it’s worth mentioning their current stack includes: SimpleDB,their pub/sub engine Simple Notification Service, Simple Queue Service, orchestration with CloudFormation, ElastiCache, Relational Database Service, Elastic Beanstalk and Elastic MapReduce. Many don’t want to admit it, but it’s the most widely used PaaS stack out there today – and arguably, the richest.

    DynamoDB & SWF are great services but represent a small portion of their platform stack.
    (BTW, I don’t include ELB, IAM or CloudWatch as Platform Services; i know some do…)