Posted by on
Categories: AWS Cloud Computing Containers google Kubernetes

#Containers may serve as functions in a @Kubernetes environment—an approach in contrast to other services. On today’s episode of The New Stack Makers streamed live from KubeCon + CloudNativeCon, we were joined by @Alex Ellis, Principal Application Developer at @ADP and Director at @OpenFaaS, and @Kassandra Perch, @IOpipe Developer Evangelist. We discussed the differences, similarities and the relative overall maturity of #serverless technologies. For those used to working with more traditional cloud-native environments and who are looking to utilize serverless technologies, having the ability to work with containers provides familiarity and stability. “Having the @Docker container as that primitive means that we can get a buy-in from the whole cloud-native community. It’s what they know, and it’s what they trust. It’s battle tested. You can just take that to production,” said Ellis. OpenFaaS gives developers the ability to package both code and binaries as serverless functions, with the flexibility to choose either Docker or Kubernetes as one’s serverless platform of choice. Sponsor Note The Cloud Native Computing Foundation (CNCF) is driving adoption of a new computing paradigm that is optimized for modern distributed systems environments, including container packaging, dynamic scheduling, and microservices-based application development and operations. Perch later went on to highlight the ways in which IOPipe is focusing on AWS Lambda, and is interested in seeing the serverless community evolve and grow. “You lose a lot of control over your application when you go with a cloud function provider like @AWS Lambda, or @Google Cloud Functions,” Perch said. “I think that’s why Kubernetes-based systems are so interesting, because you get a little bit of that control back, for better or for worse.”

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.