Leon Stigter, senior product manager for serverless at Lightbend, explained the core problem to SiliconANGLE: developers generally think of serverless as a “stateless solution,” meaning every time an application needs to do something, it has to connect to a database first. For a single service that’s manageable, but at scale, things like connection pooling get painful fast.
- stigterhq.nl/
- Blog/
- Lightbend's Akka Serverless enables stateful app development without a database - SiliconANGLE/
Lightbend's Akka Serverless enables stateful app development without a database - SiliconANGLE
·1 min·
Related
How To Secure Akka Serverless Apps With Auth0
·5 mins
As Auth0 says on their website “Identity is the front door of every user interaction”. When you’re building serverless applications, that becomes even more important since you often have multiple apps that all need to be secured. In this post I’ll walk you through how to wire up Auth0 with Akka Serverless.
How To Set Up Continuous Integration and Delivery With Github Actions and Akka Serverless
·4 mins
CI/CD is one of those things that pays for itself almost immediately. In serverless especially, where the whole point is to focus on code and let the platform handle the rest, automating your deployment pipeline is a no-brainer. It lets developers focus on code and lets the business ship quality software faster. So how does that work with Akka Serverless?
Thinking Stateful Serverless @ Micro.Sphere.IT
·1 min
As developers, we all want to be more productive. Serverless helps you do just that, by letting you focus on the business logic while shifting operations somewhere else. As more companies discover this emerging technology, we also discover drawbacks like state management. In this session, I focused on what serverless is, how it helps developers, what potential drawbacks exist, and how we can add state management into serverless.