Opinions expressed by Forbes Contributors are their own.
The Platform as a Service (PaaS) market is going through metamorphosis. A key driver of this change is the container revolution, led by Docker. Every PaaS vendor in the market has refactored its platform for containers. On the other hand, the combination of orchestration tools such as Kubernetes, Mesos, and Docker, is becoming an alternative to traditional PaaS. The line between container orchestration and PaaS is getting blurred. For enterprises and decision makers considering PaaS, the current market landscape looks complex and confusing. Amidst all this chaos, one vendor who is quietly redefining PaaS is Amazon Web Services.
Having invested heavily in the core building blocks of infrastructure – compute, storage, and networking; Amazon has been steadily moving up the stack to focus on platform services. From its vantage point, AWS has visibility into top customer use cases and deployment scenarios. By carefully analyzing what customers run in its infrastructure, AWS is building new managed services that are quickly becoming an alternative to self-hosted workloads. Amazon RDS, AWS Directory Services, Amazon Elastic File System, Amazon WorkMail, Amazon WorkDocs, and Amazon EC2 Container Service are a few examples of these services. AWS wants customers to sign-up for its managed services instead of following the DIY approach. In its current form, AWS can support everything a small and medium business needs. From hosted desktops to file sharing to collaboration to backup and archival, Amazon has it all. Beyond enterprise and business applications, it is now eyeing developers by offering a parallel universe of application lifecycle management in the cloud. The new family of code management services such as AWS CodeDeploy, AWS CodeCommit, AWS CodePipeline, handle the entire lifecycle of a cloud-native application. Amazon is in the process of building a brand new PaaS that is very different from the rest.
Amazon API Gateway – an application programming interface management layer – is the latest addition to the AWS application services portfolio. Though it might just look like another service from AWS, this has the potential to become the cornerstone of AWS’ PaaS strategy. Amazon is calling this service the “front door” for applications to access data, business logic, and functionality from back-end services. API Gateway is another classic customer workload that became a managed service on the AWS cloud. So, how does this service enable Amazon to disrupt the PaaS market?
Last year at the AWS re:Invent Conference, Werner Vogels unveiled a killer microservices platform called AWS Lambda. In a Gigaom Research report entitled Why AWS Lambda is a Masterstroke from Amazon, I analyzed the importance of this service. What’s special about Lambda is that it is a true NoOps platform. Developers bring their autonomous code snippets that get invoked by an external event. Since its inception, AWS has been regularly adding Lambda hooks for popular services like S3, DynamoDB, Kinesis, and SNS. It recently added Java language and JDK to this microservices platform. Though it was tempting to port the bulk of the business logic and workflow from monolithic apps to AWS Lambda, the service didn’t support exposing the code snippets as REST endpoints. Developers had to rely on service hooks to indirectly trigger Lambda functions.