Source: thenewstack.io
Cloudstate Is Lightbend’s Attempt to Define Serverless 2.0Category: Database, Data, Microsoft, Kubernetes
Serverless has its limits; and chief among them is management of state. I spoke to James Roper, a Cloud Architect at Lightbend and the technical lead of Cloudstate, about why stateful functions are needed — and why Lightbend has recently jumped on the serverless bandwagon.
In the KubeCon session, Bonér used the following graphic to illustrate: “The essence of the protocol approach to state management,” Bonér later clarified to me by email, “is that it is abstracting away (hiding and delegating) all the mechanics of managing the state to the backend, and leaves the user function/service to only have to care about the domain data itself — not how it is persisted, replicated, cached, made consistent, etc.
Cloudstate is an effort at standardizing stateful functions in serverless, so Lightbend will need to gather community support for it.
But it seems like Lightbend is committed to the serverless paradigm and has a lot of motivation to make its Serverless 2.0 vision stick — including that it strengthens Lightbend’s own core platform, Akka.
In the KubeCon session, Bonér used the following graphic to illustrate: “The essence of the protocol approach to state management,” Bonér later clarified to me by email, “is that it is abstracting away (hiding and delegating) all the mechanics of managing the state to the backend, and leaves the user function/service to only have to care about the domain data itself — not how it is persisted, replicated, cached, made consistent, etc.
Cloudstate is an effort at standardizing stateful functions in serverless, so Lightbend will need to gather community support for it.
But it seems like Lightbend is committed to the serverless paradigm and has a lot of motivation to make its Serverless 2.0 vision stick — including that it strengthens Lightbend’s own core platform, Akka.
Related Articles
Community Partners
DevOps Careers