Cloudstate (Part 3): Giving a Second-Thought to CRUD. In this blog post, we will take a slight detour from Cloudstate and understand why we need to give a second thought to the way CRUD operations are done in Serve.
In this blog post, we will take a slight detour from Cloudstate and understand why we need to give a second thought to the way CRUD operations are done in Serverless Computing.
Before diving deep into the need of reconsidering CRUD operations strategy in Serverless Computing, let’s first understand CRUD.
CRUD is an acronym for the four general operations that a database performs, i.e., Create, Read, Update, _and Delete_. Every web application uses CRUD operations of a database for storing/retrieving data.
However, accessing the database or doing CRUD operations in a serverless computing world is totally different. Because every User-Function that needs to R/W data would need access to the database.
Now this leaves unrestricted access to the DB with the User-Function. This means that the User-Function has to manage all the nuts & bolts of the data access & storage. Also by doing this, you are handing over the responsibility of moving all the operational concerns of the database from the Serverless framework to the User-Function.
The issues that this strategy might create are as follows:
In this blog, I’ll drive your attention towards Serverless architecture, and, then to Stateful Serverless architecture. We will see the pros and cons of such an architecture, followed by the concept of stateful serverless. Thus the title is, From Serverless to Stateful Serverless. So, let’s start with Serverless.
Akka creator & Lightbend CTO Jonas Bonér talks about challenges of bringing state to serverless, reactive microservices frameworks and Cloudstate itself.
Lightbend’s Akka Serverless running on Google Cloud provides an alternative to running a stateless middle-tier.
Businesses need to understand serverless application with major pros and cons of serverless architecture, before deciding about serverless computing.
Bypass the complex middleware and consider a lightweight node.js implementation to deploy serverless functions from your mainframe CICS applications.