3. SERVERLESS COMPUTING
Serverless computing is essentially a method for
providing backend services to developers, without
needing to run physical servers. As such, serverless
computing vendors allow the users of their services to
write and deploy code without setting up an underlying
backend infrastructure.
4.
5. SEVER VS SERVERLESS COMPUTING
•
• Remember that traditional servers have fixed resources that
users need to provision for use.
• On the other hand, serverless computing does not have fixed
resources, so it can run multiple applications from a single
server. Developers no longer need to consider the servers for
practical purposes.
6.
7. BENEFITS
There are many different advantages of utilizing serverless computing, both
for traditional Web2 development and for building dApps. Here are Some main
benefits of backend services:
• Scalability —
• When building and developing an application, there comes a time when we might need to
scale up the operations. In this case, using serverless computing is highly beneficial since
developers do not need to worry about scaling up their code. The reason for this is that the
serverless suppliers take care of the scaling on demand.
• Simple backend code —
• With serverless computing, it is simpler to create functions that independently perform a
single action, much like an API call.
8. BENEFITS
Simple backend code —
With serverless computing, it is simpler to create functions
that independently perform a single action, much like an API call.
Quicker time to market —
Utilizing a serverless architecture structure can significantly
speed up turnaround. Developers can substantially shorten
the time to market since they won’t be needing complex deploy
processes. Instead, developers can modify and add code on
a piecemeal basis.
9. DRAWBACKS
Testing and debugging —
It is in many cases hard to replicate the serverless environment to test
how the code performs once it is deployed. As developers don’t have
access to the backend structure, it makes debugging a bit more complicated.
However, when it comes to dApp development with Moralis, there are great
solutions to this problem, such as setting up a local blockchain with, for
example, Ganache
Security concerns —
As the serverless computing vendors supply the entire backend
infrastructure, it might be hard to vet the security thoroughly. This is primarily
an issue when it comes to applications handling sensitive data. However, as
Web3 development is decentralized, this is mainly an issue for traditional Web2
10. DRAWBACKS
Performance issues —
The serverless code isn’t constantly running, which means that it might
need to ”boot up” whenever it is used, which can cause performance
issues. However, if the code is constantly used, the provider will keep the code
ready.
Supplier dependence —
As a vendor provides the services, it means that developers and
companies become dependent on the providers. One example is that it
can be pretty difficult to switch vendors if necessary.