Professional Documents
Culture Documents
Aws Archi Serverless Platform Capabilities
Aws Archi Serverless Platform Capabilities
Aws Archi Serverless Platform Capabilities
cloud without having to manage the servers. AWS server less platform enables
vendors to deploy cloud solutions without server provisioning, deploying,
maintaining and monitoring applications, databases or storage servers. It contains
features like customized configuration, easy maintenance, strong security, scalability,
high availability, monitoring etc.
followed by cloud providers, where provider manages machine and resources on their
own infrastructure, and provides services via dynamic allocation of machines and
resources to build and run applications and services, which is known as “BaaS”
(Business as a service) or “FaaS” (Function as a service) where code is executed in
ephemeral Containers. Pricing is based on resources consumed during execution of
task.
CAPABILITIES OF THE AWS SERVERLESS PLATFORM
Web Applications
Build Server less web applications that automatically scale up and down and run in
highly available configuration across multiple available AWS Regions with zero
infrastructure effort required for scalability using Amazon S3, Amazon API Gateway,
AWS Lambda and Amazon DynamoDB.
SERVERLESS APPLICATION USE CASES
process the data instantaneously. AWS Lambda can be used to generate thumbnail
images, transcode videos, index files, process logs, validate content, aggregate
and filter data in real-time.
SERVERLESS APPLICATION USE
CASES
Mobile Backends
Build backend to authenticate and process API requests
Cold start — Key benefit of serverless computing is dynamic allocation of resources, due
to which vendors don’t need pay for idle time. However, sometimes this may results in
invocation latency.
Resource limits — Serverless computing imposes limits on resources memory, execution
time, bandwidth, and CPU usage, e.g. the maximum execution time per request is 900
seconds (or 15 minutes) for AWS Lambda.
Inadequate application testing — Serverless infrastructure enables to test small functions
of an application independently but it may be challenging to test the infrastructure and the
combination of all functions.
Increased security concerns — There are limited options for identifying problems and
bottlenecks if any malicious code or attack occurs on lambda functions. Developers also
have no full access over the AWS servers.
Access to the file system level — A serverless architecture isn’t the best choice for
software that requires access to the file system or operating system level. These types of
applications need to do things such as read attributes from configuration files or split in-
memory cache to disk, but serverless functions don’t allow this.Serverless functions are
stateless so whenever applications require state, serverless functions are not a good fit.