Member-only story
Service-full serverless vs no-code solutions
What is service-full serverless? And what are the differences with no-code solutions?
What is Service-full Serverless?
Service-full serverless is about using and configuring managed services and features rather than writing, testing and releasing your own code.
I would call it “integrating without glue code” for short.
In practice, an example would be using API Gateway as a proxy to directly integrate with DynamoDB [1] without writing the lambda code to integrate. However, in some cases you may need to choreograph services; then if that’s the case, Azure offers Event Grid or Logic Apps; and AWS has Event Bridge.
An interesting tangent to cover in another article is about making a distinction between choreography and orchestration, and the following slide from AWS re:Invent 2021 makes it clear:
- Orchestration is about coordinating components of distributed applications and microservices using visual workflows like Step Functions
- Choreography is about producing and consuming messages from a serverless event bus; however, services don’t need to know about each other, just about the bus
Note that not knowing about each other, reduces coupling which gives you options in the future to swap components, reduce dependency and easier testing.
If you want to read more about serverless architectures, please visit this link with a 3-article series [2].
What is low and no-code?
In addition to building applications, low/no-code platforms offer easy workflow automation, help enhance business processes, and provide other capabilities to contribute to your operations. [3]
Low-code platforms primarily speed up the development processes and enable you to jump straight into the customisation phase. Low-code also allows you to get into a bit more complicated applications. Meanwhile, no-code…
