The New Stack Podcast

Ali Ghodsi, CEO & CO-Founder at Databricks, has been a major influence in three big open source projects – Apache Mesos, Apache Spark and Apace Hadoop. What’s interesting about all of these three projects is that there are very successful companies around these projects. We sat down with Ghodsi to talk about these Open Source projects and machine learning.

According to Ghodsi, machine learning replaces manual, repeatable processes. Older systems were rule based which would bring some level of automation, but they had their own limitation. First of all, any rules-based systems can be easily gamed. Second, you can’t really use such a system to monitor and respond in situations where billions of people are interacting with each other in real time.

A chat program, which is used by teenagers can be a great example. You may want to monitor it for foul language or any alarming content; it can’t be done with rules and teenagers know how to bypass things. “Machine learning overcomes that problem and becomes a very powerful tool in such use-cases,” said Ghodsi.

Watch on YouTube: https://youtu.be/XSuJgC5DwQc

Ali Ghodsi, CEO & CO-Founder at Databricks, has been a major influence in three big open source projects – Apache Mesos, Apache Spark and Apace Hadoop. What’s interesting about all of these three projects is that there are very successful companies around these projects. We sat down with Ghodsi to talk about these Open Source projects and machine learning.

According to Ghodsi, machine learning replaces manual, repeatable processes. Older systems were rule based which would bring some level of automation, but they had their own limitation. First of all, any rules-based systems can be easily gamed. Second, you can’t really use such a system to monitor and respond in situations where billions of people are interacting with each other in real time.

A chat program, which is used by teenagers can be a great example. You may want to monitor it for foul language or any alarming content; it can’t be done with rules and teenagers know how to bypass things. “Machine learning overcomes that problem and becomes a very powerful tool in such use-cases,” said Ghodsi.

Watch on YouTube: https://youtu.be/XSuJgC5DwQc

GitOps is an iteration of DevOps as applied to cloud native and in particular Kubernetes which has a strong emphasis on declarative infrastructure, said Weaveworks CEO Alexis Richardson in this episode of The New Stack Makers. Richardson said the Weaveworks team got excited about the concept of GitOps through the ongoing management of Weave Cloud, the company's deployment, monitoring and management SaaS for containers and microservices.

The team noticed how much of the Weaveworks system was captured in Git and began exploring how they could develop a more declarative environment that captured state and allowed for continuous experimentation on the Kubernetes architecture, Richardson said. They found that the state of the code, managed in Git, allowed for better tracking and recovery when managed independently of Kubernetes. Continuous delivery approaches for Kubernetes often rely on technologies such as Jenkins.

Watch on YouTube: https://youtu.be/wJleh-6DZJ0

GitOps is an iteration of DevOps as applied to cloud native and in particular Kubernetes which has a strong emphasis on declarative infrastructure, said Weaveworks CEO Alexis Richardson in this episode of The New Stack Makers. Richardson said the Weaveworks team got excited about the concept of GitOps through the ongoing management of Weave Cloud, the company's deployment, monitoring and management SaaS for containers and microservices.

The team noticed how much of the Weaveworks system was captured in Git and began exploring how they could develop a more declarative environment that captured state and allowed for continuous experimentation on the Kubernetes architecture, Richardson said. They found that the state of the code, managed in Git, allowed for better tracking and recovery when managed independently of Kubernetes. Continuous delivery approaches for Kubernetes often rely on technologies such as Jenkins.

Watch on YouTube: https://youtu.be/wJleh-6DZJ0

GitOps is an iteration of DevOps as applied to cloud native and in particular Kubernetes which has a strong emphasis on declarative infrastructure, said Weaveworks CEO Alexis Richardson in this episode of The New Stack Makers. Richardson said the Weaveworks team got excited about the concept of GitOps through the ongoing management of Weave Cloud, the company's deployment, monitoring and management SaaS for containers and microservices.

The team noticed how much of the Weaveworks system was captured in Git and began exploring how they could develop a more declarative environment that captured state and allowed for continuous experimentation on the Kubernetes architecture, Richardson said. They found that the state of the code, managed in Git, allowed for better tracking and recovery when managed independently of Kubernetes. Continuous delivery approaches for Kubernetes often rely on technologies such as Jenkins.

Watch on YouTube: https://youtu.be/wJleh-6DZJ0

New York Times CTO Nick Rockwell is a believer in serverless technologies. He has been since the 1990s when he was using content delivery networks (CDN). In this interview for The New Stack Makers, Rockwell asserts  CDNs were designed to abstract the complexity of scaling and distributing loads much as serverless technologies promise today.

Today's serverless environments are a way to get organizations out of the business of scaling their own infrastructure. And that's very true for the New York Times. But there is confusion and it's unfortunate for Rockwell. There is this confluence of serverless and function-as-aservice technologies that creates distortion and may even be affecting developer adoption. This may also correlate when considering overall market growth in terms of developer time spent on serverless application projects.

New York Times CTO Nick Rockwell is a believer in serverless technologies. He has been since the 1990s when he was using content delivery networks (CDN). In this interview for The New Stack Makers, Rockwell asserts  CDNs were designed to abstract the complexity of scaling and distributing loads much as serverless technologies promise today.

Today's serverless environments are a way to get organizations out of the business of scaling their own infrastructure. And that's very true for the New York Times. But there is confusion and it's unfortunate for Rockwell. There is this confluence of serverless and function-as-aservice technologies that creates distortion and may even be affecting developer adoption. This may also correlate when considering overall market growth in terms of developer time spent on serverless application projects.

New York Times CTO Nick Rockwell is a believer in serverless technologies. He has been since the 1990s when he was using content delivery networks (CDN). In this interview for The New Stack Makers, Rockwell asserts  CDNs were designed to abstract the complexity of scaling and distributing loads much as serverless technologies promise today.

Today's serverless environments are a way to get organizations out of the business of scaling their own infrastructure. And that's very true for the New York Times. But there is confusion and it's unfortunate for Rockwell. There is this confluence of serverless and function-as-aservice technologies that creates distortion and may even be affecting developer adoption. This may also correlate when considering overall market growth in terms of developer time spent on serverless application projects.

CoreOS has been in the ecosystem of containerization from the very beginning. In fact it was the first company to introduce an enterprise product (Tectonic) around Kubernetes. Today Kubernetes is everywhere. Even Docker and Cloud Foundry are using it. All three major cloud providers - AWS, Microsoft Azure and Google Compute Engine support Kubernetes.

What makes Kubernetes unique? Brandon Philips, CTO and co-founder of CoreOS, explained in an interview, that traditionally Open Source technologies created commoditized alternatives to dominant closed source technologies. Kubernetes has been an exception. “Linux was a competitor to UNIX, Apache web server was a competitor to Apache IIS. What is Kubernetes competing against? There was no closed source product that we were competing against,” said Philips.

Watch on YouTube: https://youtu.be/c-EQLB_GFjE

CoreOS has been in the ecosystem of containerization from the very beginning. In fact it was the first company to introduce an enterprise product (Tectonic) around Kubernetes. Today Kubernetes is everywhere. Even Docker and Cloud Foundry are using it. All three major cloud providers - AWS, Microsoft Azure and Google Compute Engine support Kubernetes.

What makes Kubernetes unique? Brandon Philips, CTO and co-founder of CoreOS, explained in an interview, that traditionally Open Source technologies created commoditized alternatives to dominant closed source technologies. Kubernetes has been an exception. “Linux was a competitor to UNIX, Apache web server was a competitor to Apache IIS. What is Kubernetes competing against? There was no closed source product that we were competing against,” said Philips.

Watch on YouTube: https://youtu.be/c-EQLB_GFjE