Five big trends in software development: reflections from AWS re:invent 2018

Updated: Tuesday, Dec-11 2018
Tags: Technology   AWS  

 

SVG

Big picture – AWS continuing to dominate cloud

Currently at 25B run rate revenue and growing at 40%+ y/y, AWS is a juggernaut that is gaining momentum. To put this in perspective – it’s like three Salesfoces OR ten Workdays, tripling every three years. The economies of scale are clearly kicking in – AWS is churning out an impressive ~30% operating margin already, with an operating income of ~2B in Q3’18 (>8B annual run rate). AWS currently drives about 10% of Amazon’s net revenues, but more than 50% of all its operating profits.

In a space that is moving rapidly, AWS is still the key trend setter and has literally shaped the industry by being first to market with multiple services. With over 100 services today, Amazon’s velocity of innovation  and scale has changed not just the competitive dynamics of the industry, but the IT and software landscape overall. Cloud is increasingly becoming a two player race between AWS and Azure, functionality gap between them and others is growing every day across use cases  - high performance infrastructure, analytics+AI, security, hybrid+public and management. There are three main reasons for this:

  • Scale and economics – more direct customer feedback enabling faster product iteration, bigger R&D budget and better unit economics
  • Ecosystem  gravity - three sided network effects – (1) developers/enterprise deployments, (2) associated tooling/ISV integration and (3) service providers/Sis to enable migration and adoption
  • Technology and innovation - Best-in-class engineering talent and product development practices

These drivers have created an uneven playing field. While there are pockets where other vendors have certainly been at the cutting edge, almost all are struggling to play catchup, while being at a scale disadvantage.

As cloud has matured [IaaS/PaaS estimated to be a ~65B market today], most enterprises have already moved or are started their journey to the cloud. Customer focus has shifted from being “on the cloud” to being “cloud native” and evolving both their architecture and development processes to fully unlock the cloud value prop – next gen data platforms, declarative dev-ops/Infra as a Code, integrated CI/CD pipelines, live performance monitoring, automated healing etc. etc.

Being cloud native has also created a paradigm shift in how applications are architected and deployed today. The era of “server” based monolithic apps is dead. Re-developing to become microservices based was step one, the trend today is to evolve towards highly decomposed functional and serverless  architectures. This is driven by multiple reasons - (1) better infrastructure economics, (2) demanding data velocity and veracity needs of applications e.g. mobile, big data, IoT, (3) need for easier, on-demand scaling and (4) mixed interfaces and modes of consumption – e.g. mobile, voice and web.                                                                                                                                                                                                                             

It’s an exciting time in software – never before has the playing field been so level for smaller digital disruptors, who have the ability to innovate faster than ever before at a fraction of the cost.

AWS re:invent provided a glimpse on where different frameworks and software development is moving.

 

What’s hot? Five big trends from AWS re:invent

Trend I: Continued commoditization of AI and  analytics at scale

Amazon has built its ML strategy around Sagemaker, an integrated framework to design, train and deploy AI models. With inbuilt Jupyter notebooks, the framework has popular models like K-means, RCF, Gradient Boost pre-built and integrates with Tensor Flow and  Apache MXNet for neural networks/deep learning. Sagemaker makes the tedious tasks of distributed training, hyperparameter optimization and deployment extremely simple and transparent for developers.

As compared to Google and MSFT, AWS is working to make higher level AI APIs and frameworks more accessible to traditional developers. In addition to language and image recognition APIs, AWS just introduced out-of-box platforms for personalization, forecasting and document analysis/OCR – all popular AI and analytics use-cases. The efficacy of these applications are still unknown and probably not that strong today, but we expect such “AI-as a Service” platforms to continue to evolve over time and become the de-facto way a vast majority of ML use cases will be solved in the industry.

AWS is also continuing to strengthen its big data portfolio. For streaming analytics, AWS finally introduced Kafka as a fully managed AWS service. Between Kafka, Kinesis/Firehose and managed Spark– they truly have the best streaming analytics solutions in the business. From a “big data” perspective – AWS announced “Lake Formation” their fully managed data lake with inbuilt governance and cataloging.

 

Trend II: Rapid adoption of serverless and event driven compute, even in large enterprises

The most discussed technology this year was serverless. AWS took the lead here by being the first to introduce Docker support (ECS) and Lambda in 2014. Since then, the economic and agility benefits of event driven compute have become abundantly clear. There are multiple case studies of large scale deployments with full back ends and even web applications being built with a combination of AWS API Gateway and Lambdas.

Despite the hype and step improvements in tooling, developing on serverless is still a pain. There are big open challenges on developer productivity tools, security context and networking, building CI/CD pipelines and performance and error monitoring in production.

AWS has also open sourced Firecracker, their micro VM platform technology behind lambdas. This amazing piece of technology built on Linux KVM provides VM level isolation with the deployment speed of containers. It’s exciting to see how else Firecracker will be used by the industry. 

On the infrastructure side, Docker and containerization is now old news – but what’s worth nothing is the traction in the enterprise and continued improvement in container management platforms. After Docker integration, Kubernetes has emerged to be the de-facto technology for container fleet management -  all major cloud vendors have released some form of managed Kubernetes in the last two years, and this has led to an explosion of containers at scale. Alternative approaches to container management are continuing to evolve, in 2017 AWS released Fargate, it’s “Containers as a Service”, that fully abstracts the EC2 server infrastructure that containers run on. This is a powerful service gaining a lot of traction, we believe variants of this higher level approach will be the preferred way enterprises will deploy container fleets in public clouds going forward. 

 

Trend III: AWS’ tightening grip on private and hybrid usecases 

AWS is deepening its relationship with VMWare – AWS started with supporting VMWare SDDC (Software Defined Datacenter), allowing customers to transparently move VMWare workloads to AWS. They are continuing to deepen the integration e.g. AWS RDS is now available on VMWare. This positions AWS strongly for current on-prem virtualized workloads running on VMWare, which currently has about 75% market share.

Perhaps the surprise announcement was AWS outposts, a “managed appliance” based solution that goes head to head with Microsoft’s Azure stack, other hyper converged players like Nutanix and Cisco and private cloud stacks like Pivotal and Open stack. Outposts come in two flavors – VMWare and native AWS and exposes standard AWS APIs to build applications. We believe outposts will be compelling offer for CIOs and customers who are early in their cloud transformation and digital journeys, and further strengthens AWS’ position in the enterprise.

 

Trend IV: Unified and integrated platform from cloud to edge to device for IoT applications

Building production ready, bullet proof IoT applications is challenging. Architects still have to worry about multiple difficult problems - discovery, security architecture, certificate rotation, remote deployments on edge and managing intermittent and flaky connectivity.

AWS is making a serious push to unify the end-to-end IoT and edge development platform through its three frameworks 

  • Embedded: AWS RTOS (based on free RTOS), a microcontroller operating system, makes tedious things edge-discovery, certificate rotation and integrated communications transparent
  • Edge: Greengrass, which was released in 2016, is continuously being enhanced and allows transparent deployments of Lambdas to the edge. With Sagemaker Neo, Greengrass now supports AI inference at the edge through transparent, hardware optimized model deployment. (currently supports Intel, Nvidia, ARM, Cadence, Qualcomm, and Xilinx).
  • Cloud: AWS IoT core – which is all the usual data ingestion and device management tooling.

 

We believe Amazon will continue to strengthen its IoT platform and what is impressive is the growing list of hardware partners including ARM, Microchip, Texas Instruments, Infineon, STM etc. This year in addition to announcing enhancements to all their frameworks AWS announced general availability of its device qualification program for all partners, which should continue to strengthen its support matrix.

 

Trend V: Growth of use case focused, cloud native data management

Enterprises today deal with a variety of data workloads and analytical needs, and they are increasingly mixing and matching data stores to optimize costs, application performance and meet requirements. AWS is obliging in kind, rapidly expanding its data management offerings.

In addition to RDS, managed Redis/Memcached and managed Elasticache/Kibana, AWS provides a spectrum of really strong data management offerings.

  • Aurora continues to see growth in large scale deployments – it’s one of the fastest growing AWS services and has landed multiple key customers e.g. DowJones, Netflix and Capital One.
  • Dynamo continues to see success and added transactional support this year
  • Redshift, AWS’s columnar database for large scale warehousing was recently rated as the “fastest growing service in AWS’s history”  

AWS continues to meet customer needs and add to this list - it released Neptune (Graph database) last year, and announced two new specialized databases this year:

  • Quantum ledger for immutable, cryptographically verifiable writes – this covers a lot of the compliance driven industry use cases in Blockchain
  • Timestream for high performance time series analysis  

The continued innovation has put AWS in the lead vs others, particularly against traditional data management incumbents like Oracle and IBM.  


Beyond the deal terms - key questions to ask when choosing a capital partner

Updated: Monday, Jul-16 2018
Tags: Investing  

Choosing the right capital partner is critical. A good capital partner can not only help open doors to potential partners and clients but can be crucial to providing the right strategic guidance, executing your inorganic strategy and paving the way to eventual liquidity. 

Today's CEOs need to evaluate potential capital partners along multiple dimensions outside deal terms. First, PE is a very competitive industry and unless you are dealing with a top-tier VC or PE firm, most mid-market firms are fairly undifferentiated. Second, it's hard to ascertain a PE firm's capabilities and how it overlays on top of your own company's needs. Lastly, cultural fit and establishing clear alignment with goals, timelines, and priorities is challenging. 

I. What am I looking for through this capital raise

Before thinking about the right capital partner it's important to reflect and clearly articulate your strategic goals and needs:

  • What's your vision and goal for the business?
    • Exit horizon and most likely exit options
  • What key aspects of your strategy do you need support with?
    • Growth strategy
    • GTM e.g. pricing, international expansion 
    • Operations/scaling 
    • Inorganic/M&A execution - e.g. identifying potential targets, diligence and post-merger integration 
    • Exits and liquidity e.g. helping with banker selection, thinking through exit timing and options  
  • What are your own personal and economic goals
    • What are you optimizing for - economic returns, control etc.  
  • What are your working style and preferred mode of support?
    • Limited engagement 
    • Advisory through a board
    • Hands-on e.g. internal consulting engagements and hand in hand problem solving 
  • The obvious: How much capital are you raising and what are the uses of funds?  

Carefully thinking through these questions, will not only crystalize your capital raise strategy but also narrow down potential capital partners and give you a solid framework to compare your options. 

II. What are a PE/VC firm's investment underwriting criteria  

Every PE/VC fund is in the business of creating returns for their limited partners. A typical growth investment will last from 3-5 years and will look for an exit multiple of 2-3x invested capital (e.g. a min return of 50-75M for an initial investment of $25M). This simple underwriting criterion manifests itself throughout the lifecycle of investment and underpins every interaction and decision a PE firm makes. 

For example, if you are in a consolidating space and there is a chance a reasonable exit opportunity presents itself in the next two years or so, the PE firm will try to minimize its risk by either putting control provisions to block sale or by adding a security with a high liquidation preference to ensure their returns. Likewise, if there are two investors who have made investments 2-3 years apart - their investment timelines will be different and the later investor will resist a liquidity event till their underwriting criteria are met.  

Knowing what criteria are guiding an investors decision making, will not only enable you to be more strategic in negotiating terms but also help you manage expectations and difficult conversations down the road. 

III. How deeply does a PE firm know my space 

To add value beyond just capital, PE firms need to deeply understand your space and can help you scale and grow your business. Private equity firms specialize in many ways e.g. focussing on a specific vertical e.g. education, on a technology vertical e.g. Blockchain or AI and on business model/customer type e.g. B2C vs B2B. 

Most firms, however, are generalists and a majority of investment professionals don't have experience in building or bringing products to market, operating a business and might not have any depth of experience in your vertical or space, limiting the value they can bring your firm outside of a check. You need to ask multiple questions to determine the firms' capabilities:

  • Experience in specific verticals or sectors - healthcare, infrastructure software, consumer electronics etc.  
  • Operational expertise and frameworks - is the investor on your board a former operator and does he have direct experience in building/delivering products, go-to-market and managing change. Too many investors have always been 2 degrees removed from executing and will provide unactionable input. 
  • Geographical footprint and access - if you are a business looking to expand geographically, a capital partner with access and local market knowledge will potentially be a better fit. 
  • Support with inorganic growth - Identifying M&A targets, diligence, deal execution and post-merger integration. 

There are two things to keep in mind when interacting with potential investors. First, dig below the superficial conversations on GTM and market to really understand the firm's functional perspectives, knowledge of your domain. Second, ask for examples and specifics on support the investor has provided portfolio companies. It's pretty simple to differentiate a great investor, from a good one. 

IV. What is their portfolio support model 

To get the most out of your investor, you need some structure outside a quarterly board meeting. Orthogonal to how deeply a PE firm or an investor understands your space is how the firm is set up to provide portfolio support. 

PE firms' operational support for portfolio companies falls on a spectrum. On one end you have firms like Vista which have a more hands-on approach and support their portfolio companies via an internal consulting team, and often have templates and "playbooks" for different operational aspects. On the other end, you have strategic corporate venture capital, which has a more hands-free approach - often taking board seats, and mostly supporting companies through customer/partner introductions and strategic input. Other operationally focused growth equity firms like Carrick capital generally fall somewhere in between.  There are pros and cons to every model. 

In the end, a good fit is a function of three things - (1) your goals and needs, (2) your working style preference and (3) the firm's capabilities. It's important to dig in and understand the day-to-day model and ensure alignment. 

V. Who will I work with   

Like most things in life, people matter. No matter what the firm, your overall experience, and the impact a capital partner can bring are heavily dependent on the individual on your board. Not all firms are created equal and within a firm, not all partners are created equal. 

Do your diligence on the firm, but more importantly spend the time to get to know the individual.