Google Cloud & Datadog: Cloud Providers vs DevOps SaaS | In Practise

Google Cloud & Datadog: Cloud Providers vs DevOps SaaS

Former Product Leader at Google Cloud Platform

Learning outcomes

  • Core drivers and challenges of the shift to multi-cloud and hybrid
  • Layers of the DevOps stack and the trend towards one vertical solution
  • How GCP is the most open, innovative and technically astute cloud provider
  • Why third-party SaaS solutions like DataDog or Splunk have an advantage over the public cloud solutions
  • The impact of serverless technologies on the SaaS DevOps layer
  • The long run underlying risk of cloud providers entering PaaS and SaaS more aggressively as IaaS growth matures
Print

Executive profile

Deepak Tiwari

Former Product Leader at Google Cloud Platform

Deepak is a computer engineer and has experience building products for public clouds and devops stacks as a customer. Deepak spent 6 years as Product Management Leader on Google Cloud Platform where he built enterprise devops products working on Stackdriver, Cloud Logging and integrating with BigQuery. In 2017, Deepak joined Lyft as Head of Product Management where he was leading the core platform for machine learning and responsible for building out the devops infrastructure. Deepak currently works at Facebook as the Group Leader of Core ML and Ads Platform. Read more

Could you tell us about your background and experience working at Google, Lyft and Facebook?

Over the past 10 years, I have primarily worked in product development and management. I started at Google Cloud after which I moved to Lyft, where I led the product team, building internal infrastructure and platforms related to data and machine learning. At Google I worked in DevOps, specifically building tooling for the Google Cloud platform. Today I am at Facebook, working on a machine learning platform for the advertising product.

How has the level of commodification between the underlying compute layer and platform evolved over the past decade?

It has been very interesting. There are three different layers: the IaaS layer or infrastructure as a service, the platform as a service and SaaS. The overall cloud market, including SaaS, is growing quickly. The core difference of infrastructure as a service is the control over the underlying machines, allowing you to manage the operating system, hardware layer and management layer, such as virtual machines. Platform as a service focuses on the application and everything above it such as data and users, without worrying about managing the operating system kernel and other underlying objects.

SaaS removes the need to worry about the application layer, allowing you to focus on the administration control of your company. Today there is more focus on platform as a service and SaaS because that is what companies need. They are not experts in all areas and increasingly prefer to outsource. The reason why SaaS has been on fire is that organizations are now comfortable using multiple SaaS solutions. I read, recently, that companies with over 1,000 employees manage more than 100 SaaS applications, spending on average almost half a million dollars.

Infrastructure will eventually be commoditized and people will move towards platform as a service and SaaS fully-managed serverless solutions. I have also seen counter-patterns such as GCP, which started as a platform as a service. Eight years ago, the Google Cloud Platform skipped the infrastructure as a service space and went directly to platform as a service with the app engine. Developers want flexibility and want to do things on their own terms. They need that level of access to configure the infrastructure the way they prefer. Google focused more on infrastructure as a service, which is where most of the revenue comes from today.

How does the shift to multi-cloud or hybrid change cloud infrastructure?

The future is multi-cloud or hybrid, meaning multi-public cloud, on-prem plus public cloud, or on-prem plus multi-cloud. Several years ago, there was much hype around hybrid but it has not materialized that much. We felt many companies would choose the best solutions from different clouds and would patch them in a totally hybrid way, which would offer fail-over mechanisms and allow them to not run all their applications on one cloud. What if that single cloud fails, as happened with S3 a few years ago?

Everything went down, including the service which monitors all these services, because it was also dependent on S3. There are many reasons to choose multi-cloud but it has not materialized because it is hard to manage. This is why GCP is building tooling around Anthos, to offer a hybrid solution seamlessly. Multi-cloud is the future and will happen, but currently managing an application across different clouds is very difficult. Multi-cloud is being adopted by large companies such as Disney, who have different divisions running on AWS, GCP and Azure.

If they are autonomous it is possible for a ride-hailing company to run on one cloud, but their bikes and scooters unit could run on something else because of better tooling. Over the same application, companies or divisions are not yet truly multi-cloud. Some of it is also the sales muscle, because if you sign a good deal with Amazon AWS – the more you spend the higher your discount – you create the incentive to keep spending on one cloud. It is more of an 80/20 split rather than a 60/40 or 50/50.

Why is it technically so difficult to have multi-cloud?

Sign up to read the full interview and hundreds more. No credit card details required.
Sign up to read

Audio

Google Cloud & Datadog: Cloud Providers vs DevOps SaaS

September 1, 2020

00:00
00:00
Sign up to listen to the full interview and hundreds more. No credit card details required.
Sign up to listen