Scalability: Developers don’t need to build in their own autoscaling
policies or technologies. The provider is responsible for adding more
capacity on demand.
Easier to use and write code for: Small teams of developers can
use serverless deployment without needing to involve infrastructure
teams or acquire advanced skills.The following are some of the disadvantages of serverless
deployment:
Latency: Spin-up time from idle for the function can cause significant
delays that must be accounted for in application design.
Resource constraints: Some workloads need more resources than
the service may typically be allocated for, causing heavy charges, which
may make it cheaper to dedicate infrastructure.
Monitoring and debugging: There is limited visibility into the
underlying infrastructure, which makes it difficult to troubleshoot
performance issues with the application. You are often limited to the
tools provided by the service provider, which are likely to be
proprietary.
Security and privacy: Most providers are built on proprietary
offerings and use shared resources. Misconfiguration can result in
compromises and data loss, just as with any other cloud service. There
are on-premises options for serverless that can give businesses more
control over their data and security posture.
Vendor lock-in: This is a big one. Each provider has its own tools and
frameworks, which makes it very difficult to switch providers if costs go
up or if services are not working as planned. Migration between
providers is not trivial.DEVOPS
Agile has dramatically changed the software
development landscape by introducing a more efficient
and faster way of delivering software and value to the
business. Much of the improvement in the development
process has been focused on delivery speed. You can
have as much Agile development as you want, but if you
can’t get the software deployed in a timely manner, you
can’t take advantage of its capabilities. Software was
traditionally built and tested by developers, and if it
worked on their laptops or test systems, it was pitched
over the fence to IT operations for deployment. When
things did not go as smoothly as planned, a significant
amount of finger-pointing would ensue. Developers