While there’s still a lot of uncertainty about the viability of platform-as-a-service (PaaS) offerings as a distinct market apart from infrastructure-as-a-service (IaaS), there is no doubt that PaaS technologies are becoming more accessible in the cloud with each passing day.
With the recent explosion of cloud computing services, developers now have more opportunities than ever to take advantage of enterprise-scale computing platforms. However, most cloud computing services, such as Amazon's Elastic Compute Cloud (EC2), have unique and incompatible APIs. This has provided a challenge for organizations wanting to develop in-house applications that can later be seamlessly deployed directly to Amazon's service when necessary. For example, Ubuntu Server, a Linux-based operating system supported by Europe's Canonical Ltd, is the most widely deployed operating system on EC2, yet there has been no way for developers to create private, EC2-compatible cloud computing systems internally with Ubuntu.
At first, the phrase "my API is my Product" seems misleading. An API is a way to deliver a product, rather than the product itself, right? The term designates a "set of programming instructions designed to access an app." Period. We're talking about a means, rather than an end. That's why there are so many different products relying on APIs: Twilio for phone, Mailjet for email, Google Maps for maps, etc.