Josh Thorngren, vice president of marketing at Twistlock, said his team ran a booth at the event specifically to participate in the discussions around serverless solutions. Twistlock offers security and vulnerability analysis for the entire development lifecycle and specifically focuses on solving the problems inherent to governance and enforcement of security policies in cloud environments.
Thorngren said he sees a lot of the discussion to be focused on serverless as a tool to supplement container-based architectures, but not necessarily to replace them. “We are actively moving from containers into serverless as a space. Just last week, we released a beta to our existing customers giving them the ability to do the same vulnerability management for their serverless functions as they can for their container applications. A lot of that overlaps with how companies are delivering functions with things like Amazon Lambdas,” said Thorngren.
The real advantage of the language, said Kelly, is that large teams of developers can make sense of mountains of code. This is because type safety and other enhancements to the language ensure that misprints, misspellings, and other potential coding errors can be more easily identified because they are caught at compile time.
“There are large enterprise engagements with Node already, as evidenced by the things we see in our own cloud. Node is used for everything from connecting up services in Watson, to creating all sorts of serverless projects with OpenWhisk. It’s become a standard language, and one of the most heavily used tools in the toolbox these days. It’s penetrated big old Java shops,” said Moore.
Moore said that IBM is fully backing OpenWhisk as its serverless solution. He said that he expects standards to arise around serverless compute, and that portability across clouds will be highly important in the future of cloud functions.
Moore said, with serverless, the industry needs to “Get to standardized eventing. The event model needs to be standardized. We have a whole series of these things popping up and getting us all together to work on that issue and create some consistency there allows that programming model to take off. I like the fact we’ve introduced rules into the OpenWhisk construct so you can use rules to do transforms and things on what’s happening as a result. I think that’s very powerful,” said Moore.
Twistlock is a sponsor of The New Stack.
Feature image via Pixabay.