The companies will offer a single-pane control panel over their container and serverless computing platforms. It will rely on Joyent’s Triton Kubernetes platform and LunchBadger’s application stack for management.
Joyent’s Triton Kubernetes platform provides multi-cloud compute using Kubernetes as the delivery vehicle. It allows customers to provision and manage Kubernetes clusters in both public and private cloud environments.
Samsung last year acquired Joyent as a way to expand its cloud operations and reduce costs. As part of the deal, Samsung became Joyent’s largest client, decreasing its previous reliance on Amazon Web Services (AWS) and Microsoft Azure for cloud services.
The LunchBadger stack includes an API gateway built on Express.js, which is a web application framework for Node.js; microservices composition and integration tooling; a developer portal and integrated developer environment to write functions; and a Kubernetes runtime to abstract low-level technical details in a container.
Al Tsang, founder and CEO of LunchBadger, said the partnership provides an agnostic alternative to current serverless platforms. These include AWS Lambda, Google Functions, Microsoft Azure Functions, and IBM Openwhisk.
Tsang explained that combining its serverless expertise with Joyent’s Kubernetes work allows for it to serve both microservices platforms.
“The value is that the infrastructure play is table stakes with Kubernetes,” Tsang explained of the combined offering. “We have had two-plus years working with Kubernetes and can now offer enterprises a single-pane of glass to manage all of their microservices, whether they are in containers or using serverless.”
LunchBadger was founded last year, with Tsang previously serving as CTO at StrongLoop. The firm earlier this year raised $1.5 million in funding from Pelion Ventures.
Integration of containers and serverless into current cloud environments has been an ongoing issue for vendors and organizations. Tsang admitted that LunchBadger did not have enterprise expertise to penetrate that market, which it has gained from partnering with Joyent.
Nate Taggart, co-founder and CEO of serverless-focused vendor Stackery, recently noted that enterprise integration issues included uncertainty into how serverless architectures can be integrated into current cloud and container operations; and a basic lack of familiarity for management and control over deployments.
“Serverless is still in its early stages,” Taggart said. “This is a new skillset that needs to be mastered, and by putting in place some familiarity it allows enterprises to be more comfortable, quicker.”
Charlie Li, chief cloud officer at Capgemini, explained this market confusion has handicapped the adoption curve of serverless compared with that of containers.
“We will see in a year,” Li said. “It may even be two years before there is mass adoption of serverless. All of our clients are expressing interest in trying serverless, but outside of a few new applications being launched and some PoCs, mass adoption is still some time away.”
Tsang indicated that it was only a matter of time as enterprise interest in serverless was indeed robust.
“It’s really one of the few new technologies I have seen that has generated a real enterprise following before it’s really ready for use,” Tsang said.
Cloud providers have moved to goose adoption, unveiling updates designed to allow for tighter integration into host cloud deployments.
However, Tsang said many of those platforms are too tightly integrated, which limits an enterprise to being locked into a specific host provider for further development. A recent 451 Research report found a multi-cloud approach could save enterprises up to 74 percent compared with using a single cloud provider.
“Lambda has four or five components that make it work,” Tsang explained. “We have now basically open sourced those to provide a better experience for customers and allows them to avoid lock-in.”