About Unbundling AWS
Over the past year, I have spent a lot of time digging into cloud infrastructure and technical tools as a space for investing. One of the emergent behaviors of technology trends is the accelerating advantage of being a winner, played out with network effects or scale effects (or both!). Since its mid-2000ās launch, AWS has obviously become a juggernaut, growing so quickly and throwing off so much cash that even Amazon canāt put it to work fast enough (!). Getting a new software product to market has never been as cheap or fast as it is today, despite the fact that the surface area of in-depth knowledge required to build high-performing software has never been higher.
Leveraging lessons from building Amazonās existing infrastructure, AWS has amassedĀ almost 50% market shareĀ of public cloud spending. It started out offering a small handful of services (S3, SQS, and EC2), but now hasĀ 170 discrete servicesĀ spanning 23 categories (and these are only the public ones!) As an early-stage investor, Iām hard-pressed to name any tectonic shifts that have had as much impact on startup formation. The availability of open-source tooling and the ease of access to infrastructure on AWS and other IaaS providers, and infrastructure turning into software, which means itās programmable and, increasingly, thinly-sliced.
Recently, when I opened the AWS Console, I had a moment ofĀ deja vuĀ that called back to a 2010 post by Andrew Parker, then of Spark Capital, that focused on theĀ startup opportunities of unbundling Craigslist. And it shifted a long-simmering feeling into focus for me:Ā I am really excited about startups that are unbundling AWS.
AWSās growth has started slowing a bit, perhaps due to saturation, perhaps due to competition. Or perhaps it is because [my theory] as they continue to expand into platform-type services, some of their offerings shift from being best-in-class to being very reliable and with a ājust-ok-but-well-integratedā user experience. This is a great way to make money, but it also leaves certain of the ācategoriesā on the homepage open to outmaneuvering by a best-in-class experience.
I need to map out something like the awesome graphics that the Spark folks produced for Craigslist, but for now, I have been exploring my intuition about where and why there will be pieces of AWS that will be subject to unbundling. Here are a few that have come to mind already:
- Frameworks and deployment tools that make application software agnostic to the underlying infrastructure provider. Things like theĀ Serverless framework, containers + orchestration, or IAC tools likeĀ Saltstack,Ā Terraform,Ā Ansible, etc
- The overlapping areas of logging, APM, and monitoring. This is a hot area right now, with IPOās likeĀ DynatraceĀ orĀ Datadog, or acquisitions likeĀ SignalFX. Related:Ā Cloudwatch is terrible!
- Data science workflows ā this is my subjective, anecdotal experience, but most data scientists I know have a preference for Google Cloud for a lot of their work, andĀ custom hardware like TPUsĀ likely play a role here
- Authentication and identity āĀ Auth0,Ā LoginRadius,Ā Okta, etc ā¦ where it may make sense to have a third-party handle
- Paradigms that lead to different stack choices ā Iām a big proponent of theĀ JAMstack, and itās a prime example of a paradigm where AWS may not be a natural choice for parts of this architecture. I believe that we will continue to see this and other new architectural paradigms evolve
There are obvious differences between Craigslist and AWS. The most important is that Craigslist (and each of the category spawn) is a marketplace, and so has the powerful advantage of network effects. Another distinction is that AWS has relative cost advantages over its unbundlers when it comes to the fundamental components of infrastructure (compute, bandwidth, storage, etc.), and I canāt see a parallel to Craigslist. So itās not a perfect analogy, but the premise of unbundling certain categories still holds.
But what if Amazon launches a competing product?
This is one of those classical questions for any startup. In general, I donāt get too worried about $BIGCO being the reason that a startup dies. In my experience, itās pretty far down the list ofĀ things that actually kill startups. That said, particular to developer-facing startups, there might be some reason for concern. AWSās relationship with open source is ā¦Ā complicated. Notably, Mongo and Redis have both had to maneuver to combat AWS. The thing to note here is that in both of those situations, itās a problem that those companies have had to face as theyĀ monetize, and was not a barrier to adoption. Put another way: we should all be so lucky to be at a scale and level of popularity where this becomes a problem. Itās hard for me to see a lot of cases where AWS will be competing with companies before they reach scale.
Back to the future
Thinly-sliced? Purpose-built, best-in-class tools? Sound familiar?
ā¦ elaborate computing tasks are typically composed from loosely coupled small parts, often software tools taken off the shelf.
TheĀ UNIX philosophyĀ strikes back! The history of software development has a lot of patterns in it, and this trend toward tools and component parts that do one thing well is one of my favorite. If every part of our infrastructure is available in ever-smaller pieces, on-demand, then the long narrative arc of this philosophy ought to continue to win out.
There are already billion-dollar companies that focus on relatively narrow niches within the AWS offering spaceāand I believe there will be many, many more.Ā If youāre building something that carves out a piece of AWS, I want to talk to you.