The New Stack Podcast

Billions of clock speeds run on an edge processor in between network packets, said Chris Sachs, founder of Swim.ai in this episode of The New Stack Makers. The capacity is seemingly timeless. The cloud isn’t meant for processing and analyzing data from nodes in real-time. The data that is processed at the edge from a node requires a fundamental different approach.

Swim.ai’s platform uses software that treats every node as a digital twin. These “actors” are configured as a software kernel, fully configured. They maximize the process clock speeds to use every network packet and CPU cycle to its advantage. It is fully self-contained, a raw compute platform that looks at data from the nodes on the edge.

Swim.ai does real-time data processing by implementing an actor framework that all have their own state -- just enough to maximize all those clock speeds and analyzing it with neural networks that work across intersections, said Swim.ai’s Simon Crosby, who also joined us for the interview.

The capability to process data at the edge allows to create learning environments such as with predicting traffic in a city like Palo Alto, which Sachs and Crosby discuss in particular in this podcast and demonstration.

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

Billions of clock speeds run on an edge processor in between network packets, said Chris Sachs, founder of Swim.ai in this episode of The New Stack Makers. The capacity is seemingly timeless. The cloud isn’t meant for processing and analyzing data from nodes in real-time. The data that is processed at the edge from a node requires a fundamental different approach.

Swim.ai’s platform uses software that treats every node as a digital twin. These “actors” are configured as a software kernel, fully configured. They maximize the process clock speeds to use every network packet and CPU cycle to its advantage. It is fully self-contained, a raw compute platform that looks at data from the nodes on the edge.

Swim.ai does real-time data processing by implementing an actor framework that all have their own state -- just enough to maximize all those clock speeds and analyzing it with neural networks that work across intersections, said Swim.ai’s Simon Crosby, who also joined us for the interview.

The capability to process data at the edge allows to create learning environments such as with predicting traffic in a city like Palo Alto, which Sachs and Crosby discuss in particular in this podcast and demonstration.

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

Billions of clock speeds run on an edge processor in between network packets, said Chris Sachs, founder of Swim.ai in this episode of The New Stack Makers. The capacity is seemingly timeless. The cloud isn’t meant for processing and analyzing data from nodes in real-time. The data that is processed at the edge from a node requires a fundamental different approach.

Swim.ai’s platform uses software that treats every node as a digital twin. These “actors” are configured as a software kernel, fully configured. They maximize the process clock speeds to use every network packet and CPU cycle to its advantage. It is fully self-contained, a raw compute platform that looks at data from the nodes on the edge.

Swim.ai does real-time data processing by implementing an actor framework that all have their own state -- just enough to maximize all those clock speeds and analyzing it with neural networks that work across intersections, said Swim.ai’s Simon Crosby, who also joined us for the interview.

The capability to process data at the edge allows to create learning environments such as with predicting traffic in a city like Palo Alto, which Sachs and Crosby discuss in particular in this podcast and demonstration.

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

Justin Johnson is development director at StackPath and our guest on this latest episode of The New Stack Makers, recorded at the Open Source Leadership Summit in March. StackPath acquired companies in the CDN, software and security market to manage deployment of content and applications across its infrastructure. Positioning itself as a security as a service, StackPath is using open source technologies to interconnect the different products it has acquired into one single platform. Customers write code to the StackPath APIs, which then manage the content and applications across its distributed network, as opposed to one big data center, or one big pipe.

The longer the distance traveled to the user, the more latency. The limits of livestreaming lies in the distance large files have to travel to the user. There are different types of workloads that require different networks. For example, Microsoft works with StackPath to update Xbox machines. To do so efficiently requires an infrastructure that can distribute the load as close as possible to the device, Johnson said. It's that last mile that is the biggest challenge.

Coming up, The New Stack will be live at Cloud Foundry Summit, KubeCon + CloudNativeCon, OpenStack Summit and ChefConf. We’ll be podcasting, hosting pancake breakfasts and spending a lot of time talking with people. Thanks to all our sponsors who make our work possible here at The New Stack.

Chef, Cloud Foundry, KubeCon+CloudNativeCon, Microsoft and OpenStack are sponsors of The New Stack.

Justin Johnson is development director at StackPath and our guest on this latest episode of The New Stack Makers, recorded at the Open Source Leadership Summit in March. StackPath acquired companies in the CDN, software and security market to manage deployment of content and applications across its infrastructure. Positioning itself as a security as a service, StackPath is using open source technologies to interconnect the different products it has acquired into one single platform. Customers write code to the StackPath APIs, which then manage the content and applications across its distributed network, as opposed to one big data center, or one big pipe.

The longer the distance traveled to the user, the more latency. The limits of livestreaming lies in the distance large files have to travel to the user. There are different types of workloads that require different networks. For example, Microsoft works with StackPath to update Xbox machines. To do so efficiently requires an infrastructure that can distribute the load as close as possible to the device, Johnson said. It's that last mile that is the biggest challenge.

Coming up, The New Stack will be live at Cloud Foundry Summit, KubeCon + CloudNativeCon, OpenStack Summit and ChefConf. We’ll be podcasting, hosting pancake breakfasts and spending a lot of time talking with people. Thanks to all our sponsors who make our work possible here at The New Stack.

Chef, Cloud Foundry, KubeCon+CloudNativeCon, Microsoft and OpenStack are sponsors of The New Stack.

Justin Johnson is development director at StackPath and our guest on this latest episode of The New Stack Makers, recorded at the Open Source Leadership Summit in March. StackPath acquired companies in the CDN, software and security market to manage deployment of content and applications across its infrastructure. Positioning itself as a security as a service, StackPath is using open source technologies to interconnect the different products it has acquired into one single platform. Customers write code to the StackPath APIs, which then manage the content and applications across its distributed network, as opposed to one big data center, or one big pipe.

The longer the distance traveled to the user, the more latency. The limits of livestreaming lies in the distance large files have to travel to the user. There are different types of workloads that require different networks. For example, Microsoft works with StackPath to update Xbox machines. To do so efficiently requires an infrastructure that can distribute the load as close as possible to the device, Johnson said. It's that last mile that is the biggest challenge.

Coming up, The New Stack will be live at Cloud Foundry Summit, KubeCon + CloudNativeCon, OpenStack Summit and ChefConf. We’ll be podcasting, hosting pancake breakfasts and spending a lot of time talking with people. Thanks to all our sponsors who make our work possible here at The New Stack.

Chef, Cloud Foundry, KubeCon+CloudNativeCon, Microsoft and OpenStack are sponsors of The New Stack.

Tracing, logging, monitoring are all getting re-invented with the advent of container-native environments, said Evan Powell on this episode of The New Stack Makers. The force of re-invention is also running through the storage and management layers with new thinking about the concept of container storage.

Powell is CEO of MayaData, formerly CloudByte. MayaData is behind OpenEBS, an open source container storage environment that allows every workload and storage team to have its own controller. The company has about 75 engineers, mostly out of Bangalore, India. MayaData has a similar strategy to companies like MongoDB, which fostered an open source project and with that as its base built a commercial SaaS platform.

MayaOnline is a free platform that gives developers a view into their OpenEBS or Kubernetes stateful workload environments. MayaOnline gives developers views into how systems are behaving. For Maya, the service can see the clickstreams, giving a view into how developers are using the service. A SaaS platform to manage OpenEBS is in development.

Tracing, logging, monitoring are all getting re-invented with the advent of container-native environments, said Evan Powell on this episode of The New Stack Makers. The force of re-invention is also running through the storage and management layers with new thinking about the concept of container storage.

Powell is CEO of MayaData, formerly CloudByte. MayaData is behind OpenEBS, an open source container storage environment that allows every workload and storage team to have its own controller. The company has about 75 engineers, mostly out of Bangalore, India. MayaData has a similar strategy to companies like MongoDB, which fostered an open source project and with that as its base built a commercial SaaS platform.

MayaOnline is a free platform that gives developers a view into their OpenEBS or Kubernetes stateful workload environments. MayaOnline gives developers views into how systems are behaving. For Maya, the service can see the clickstreams, giving a view into how developers are using the service. A SaaS platform to manage OpenEBS is in development.

Tracing, logging, monitoring are all getting re-invented with the advent of container-native environments, said Evan Powell on this episode of The New Stack Makers. The force of re-invention is also running through the storage and management layers with new thinking about the concept of container storage.

Powell is CEO of MayaData, formerly CloudByte. MayaData is behind OpenEBS, an open source container storage environment that allows every workload and storage team to have its own controller. The company has about 75 engineers, mostly out of Bangalore, India. MayaData has a similar strategy to companies like MongoDB, which fostered an open source project and with that as its base built a commercial SaaS platform.

MayaOnline is a free platform that gives developers a view into their OpenEBS or Kubernetes stateful workload environments. MayaOnline gives developers views into how systems are behaving. For Maya, the service can see the clickstreams, giving a view into how developers are using the service. A SaaS platform to manage OpenEBS is in development.

Today on the New Stack Analysts we have a combined package of two interviews I recently did with Daniel Bryant and Matt Chotin. Bryant is one of the people The New Stack looks to for his insightful analysis. He is an independent consultant, speaker and writer. Chotin is a well-respected technologist who works as senior director of developer initiatives at AppDynamics, where he is responsible for leading AppDynamics "products to better support developers in improving improving performance and achieving business outcomes." Our topic of discussion for this podcast: When discussing microservices, how would you characterize the state of the market?

The wave of development interest in containers is growing as financial investment also grows. We first discuss the state of the market with Bryant, followed by Chotin who talked to the overall maturity of the users who are developing microservices.

More microservices means a lot more containers in all stages of development, deployment and management. That ultimately is great news for the developer tool community. People are building continuous delivery models based on DevOps practices delivered across any thinkable possible infrastructure. It’s these DevOps practices that will remain largely cultural as the board room transfixes on digital transformation and uses that paradigm as the basis for spending over time.