Introduce about cloud service adoption for Thailand and globally. What is the factor to transform modernize cloud technology and how to work with it? Then, we talking about the definition of Serverless service on public cloud provider and example success solution design on cloud-native application that include Serverless service in a mainly design.

1. SERVERLESS CLOUD ADOPTION
C LO U D I N D U S T R Y T H A I L A N D
B y W a t c h a r i n Ya n g N g a m
@ O c t 2 0 2 3

2. WATCHARIN YANG-NGAM (START)
D E V O P S C O N S U LTA N T & C L O U D S O L U T I O N
Graduated: KMITL#59
Work experience:
• 2 year in Network Engineer
• 5 year in Dev(Sec)Ops Consultant & Cloud Solution
Architect
Certificated:
• AWS Certified Solutions Architect – Associate
• AWS Certified DevOps Engineer – Professional
• Google Cloud Certified - Professional Cloud Architect
• Professional Cloud DevOps Engineers
• Developing a Google SRE Culture
2

3. AGENDA
T H A I L A N D C LO U D A D O P T I O N
B E C O M I N G TO S E RV E R L E S S
S E RV E R L E S S S E RV I C E
C H A L L E N G I N G
C A S E S T U DY
L E A R N I N G PAT H
G A M E
C O N C LU S I O N
3

4. THAILAND CLOUD ADOPTION
T E C H I N D U S T R Y S I T U AT I O N
End-user spending on public cloud in Thailand
has been growing rapidly in recent years, and
this trend is expected to continue in the coming
years.
4

5. SERVICE CHART
5

6. WORLDWIDE PUBLIC CLOUD SERVICES
END-USER SPENDING FORECAST
Services 2021 2022 2023
Cloud Business Process Services (BPaaS) 54,952 60,127 65,145
Cloud Application Infrastructure Services (PaaS) 89,910 110,677 136,408
Cloud Application Services (SaaS) 146,326 167,107 195,208
Cloud Management and Security Service 28,489 34,143 41,675
Cloud System Infrastructure Services (IaaS) 90,894 115,740 150,254
Desktop-as-a-Service (DaaS) 2,059 2,539 3,104
Total Market 412,632 490,333(18.83%) 591,794(20.69%)
6
*unit is Millions of U.S. Dollars
Source: Gartner (October 2022)

7. WORLDWIDE PUBLIC CLOUD SERVICES
END-USER SPENDING FORECAST
0
100,000
200,000
300,000
400,000
500,000
600,000
700,000
2021 2022 2023
Axis
Title
Growth spending
Cloud Business Process Services (BPaaS)
Cloud Application Infrastructure Services (PaaS)
Cloud Application Services (SaaS)
Cloud Management and Security Service
Cloud System Infrastructure Services (IaaS)
Desktop-as-a-Service (DaaS)
Total Market
7

8. F O R E C A S T: P U B L I C C L O U D S E R V I C E S ,
W O R L D W I D E , 2 0 2 0 - 2 0 2 6 , 3 Q 2 2 U P D AT E .
ACCORDING TO GARTNER, PUBLIC CLOUD SPENDING IN THAILAND IS
EXPECTED TO REACH 54.4 BILLION BAHT IN 2023, UP FROM 41.3
BILLION BAHT IN 2022. THIS REPRESENTS A GROWTH RATE OF 31.8%,
WHICH IS HIGHER THAN THE GLOBAL GROWTH RATE OF 20.7%.

9. THAILAND POPULAR
SERVICES
I A A S
INFRASTRUCTURE AS
SERVICE
D A A S
DESKTOP AS SERVICE
PA A S
PLATFORM AS SERVICE
B PA S
BUSINESS PROCESS AS
SERVICE
S A A S
SOFTWARE AS SERVICE
9

10. 5 KEY BENEFIT TO CLOUD ADOPTION
1. Scalability and agility: The cloud offers businesses the ability to scale their IT resources up or down quickly and easily,
depending on their needs. This can be a major advantage for businesses that experience seasonal fluctuations in demand.
2. Cost savings: The cloud can help businesses save money on IT costs in a number of ways. For example, businesses can avoid
the upfront costs of purchasing and maintaining their own IT infrastructure.
3. Security and compliance: Cloud providers offer a wide range of security features and compliance certifications.
4. Innovation: The cloud gives businesses access to the latest IT innovations without having to invest in their own
infrastructure. This can help businesses to stay ahead of the competition and to improve their customer experience.
5. Global reach: The cloud allows businesses to deploy their applications and data to users around the world. This can help
businesses to expand into new markets and to better serve their global customers.
12

11. BEHAVIOR CLOUD ADOPTION IN THAILAND
I N C R E A S E D A D O P T I O N O F I A A S S E R V I C E S G R O W T H O F PA A S A N D S A A S S E R V I C E S
13
C L O U D - N AT I V E A P P L I C AT I O N S A N D S E R V I C E S I N C R E A S E D U S E O F H Y B R I D A N D M U L T I - C L O U D

12. INCREASED ADOPTION OF IAAS
SERVICES
IaaS services are the most popular
type of public cloud service in
Thailand. Businesses are using IaaS
services to provision and manage
their IT infrastructure on demand.
14

13. GROWTH OF PAAS AND SAAS SERVICES
PaaS and SaaS services are
becoming more popular in
Thailand as businesses look to
offload the management of their IT
infrastructure and applications.
15

14. ADOPTION OF CLOUD-NATIVE
APPLICATIONS AND SERVICES
Businesses in Thailand are
increasingly adopting cloud-native
applications and services. These
applications and services are
designed to be deployed and
managed in the cloud.
16

15. INCREASED USE OF HYBRID AND
MULTI-CLOUD
Businesses in Thailand are
increasingly using a hybrid and
multi-cloud approach to cloud
computing. This allows them to
take advantage of the best
features of different cloud
platforms.
17

16. BREAK!
18

17. BECOMING TO SERVERLESS
R E V O L U T I O N O F C L O U D S E R V I C E
Understanding about our journey on public
cloud service from a part to currently
innovations
19

18. VM & CONTAINER & SERVERLESS
20

19. TIMELINE FOR RELEASED CLOUD
SERVICE AWS
21
2006 - 2012
Released cloud
Infrastructure as Service like
S3, EC2, RDS, VPC,
CloudFront and Other.
2013
Released Serverless service
as Lambda and RedShift
2014
Released Container
platfrom as ECS and EKS
2015 - 2023
Released more Serverless
service as Aurora, Athena,
Amplify, Rekognition,
SageMaker and Other.

20. WHAT’S
PURPOSE THAT
WE TRANSFORM?
W E H A V E B E E N T O R E D U C E A P P S I Z I N G
22

21. WHAT YOU THINK ABOUT IT?
23

22. THE EVOLUTION OF APIS
Function
and
Procedures
RPC
SOA
APIs
Event and
Streaming
Event APIs
24
EJBs
Web application
Microservices
Serverless

23. IAAC COMMUNICATION
RESTful APIs:
• Representational State Transfer (REST) is an architectural
style for designing networked applications.
• RESTful APIs use standard HTTP methods (GET, POST, PUT,
DELETE) to perform CRUD (Create, Read, Update, Delete)
operations on resources.
• They are based on stateless client-server communication, and
data is typically exchanged in JSON or XML formats.
25

24. IAAC COMMUNICATION
WebSocket and Real-Time APIs:
• WebSocket is a communication protocol that enables
bidirectional, full-duplex communication between a client
and a server over a single, long-lived connection.
• Real-time APIs use WebSocket or similar technologies to
deliver real-time updates, such as chat messages,
notifications, or live data feeds.
• They are suitable for applications where instant updates are
critical, such as messaging apps, online gaming, and
collaborative tools.
26

25. CAAC COMMUNICATION
GraphQL:
• GraphQL is a query language for APIs that allows clients to
request only the data they need.
• It provides a more efficient and flexible way to retrieve data,
reducing over-fetching and under-fetching of information.
• Clients can compose complex queries, fetching data from
multiple sources with a single request.
27

26. CAAC COMMUNICATION
gRPC:
• gRPC services and messages between clients and servers are
defined in proto files. The Protobuf compiler, protoc,
generates client and server code that loads the .proto file
into the memory at runtime
• Streaming is another key concept of gRPC, where many
processes can take place in a single request. The multiplexing
capability of HTTP/2 makes it possible.
28

27. FAAC COMMUNICATION
Event-Driven APIs:
• Event-driven APIs use the publish-subscribe pattern to
facilitate asynchronous communication between components
or microservices.
• These APIs enable the broadcasting of events when specific
actions occur and interested parties (subscribers) receive and
react to those events.
• Event-driven architecture is highly scalable, resilient, and
decouples components, making it suitable for complex and
distributed systems.
29

28. KEY FACTOR MAKE THEM HAPPEN
EFFICIENCY
 Containers can start up and run faster than VMs
 They require less memory and CPU resources.
 Function is faster than both types
 Function is lean of sizing and resources
SCALABILITY
 Container can be easily spun up and down as needed with few
minute
 Function can be immediate spawn process to handle events.
30

29. KEY FACTOR MAKE THEM HAPPEN
PORTABILITY
 Containers are not tied to a specific hardware platform.
 Functions are not specifying any infrastructure layer.
COST OPTIMIZE
 Container can sharing a pooling resources in same infrastructure.
 Functions is make you pay-per-use only related on application
processing.
31
This Photo by Unknown Author is licensed under CC BY-SA

30. BREAK!
32

31. SERVERLESS TRANSFORMATION
S E R V E R L E S S M I G R AT I O N S T R AT E G Y
Customers migrating to the cloud often want to
get the benefits of serverless architecture. But
what is the best approach and is it possible?
There are many strategies to do a migration
33

32. D E F I N I T I O N S
CLOUD SERVERLESS IS A CLOUD COMPUTING EXECUTION MODEL THAT
ALLOWS DEVELOPERS TO BUILD AND RUN APPLICATIONS WITHOUT HAVING TO
PROVISION OR MANAGE SERVERS. SERVERLESS SERVICES ARE TYPICALLY
EVENT-DRIVEN, MEANING THAT THEY ARE TRIGGERED BY EVENTS SUCH AS
HTTP REQUESTS, DATABASE UPDATES, OR MESSAGES FROM OTHER SERVICES.

33. CORE COMPONENTS
COMPUTE
Serverless computing services provide a compute platform
for running applications without having to provision or
manage servers. This is typically done using containers,
which are lightweight and isolated execution environments.
STORAGE
Serverless computing services also provide storage for
application data. This storage is typically managed by the
cloud provider and is highly scalable and reliable.
35

34. CORE COMPONENTS
DATABASES
Serverless computing services also provide managed
database services. This allows developers to use databases
without having to provision or manage them themselves.
MESSAGING
Serverless computing services also provide messaging
services. This allows applications to communicate with each
other and with other services in a reliable and scalable way.
36

35. CORE COMPONENTS
EVENTING
Serverless computing services are typically event-driven.
This means that applications can be triggered by events
such as HTTP requests, database updates, or messages from
other services.
37

36. B E N E F I T S T O T R A N S F O R M I N G
SERVERLESS COMPUTING HAS GAINED POPULARITY
AS A SERVICE ON PUBLIC CLOUDS DUE TO SEVERAL
KEY FACTORS

37. KEY BENEFIT
• Simplified Development
Serverless platforms abstract away infrastructure
management, allowing developers to focus solely on
writing code.
• Scalability
Serverless services automatically scale to handle varying
workloads. This elastic scaling ensures that applications can
handle a sudden increase in traffic without manual
intervention.
39
• Event-Driven Model
Serverless architectures are inherently event-driven
architect. Functions are triggered in response to specific
events, such as HTTP requests, file uploads, or database
changes.
• Integration with Managed Services
Serverless platforms often integrate seamlessly with other
managed services offered by cloud providers, including
databases, storage, authentication, and monitoring. This
simplifies the development of end-to-end solutions.

38. KEY BENEFIT
• Cost Efficiency
With serverless, you only pay for the compute resources
used during the execution of your functions. There are no
fixed costs associated with maintaining servers or VMs,
which can lead to significant cost savings, especially for
applications with sporadic or variable workloads.
• No Server Management
Serverless was removal of server management tasks, such
as provisioning, patching, and maintenance. This allows
developers and organizations to shift their focus from
infrastructure concerns to creating and improving
applications.
40
• Serverless Frameworks and Tooling
Various serverless frameworks, like the Serverless
Framework and AWS SAM, provide tools and templates for
simplifying serverless application development and
deployment. These frameworks help standardize and
streamline the process.
• Global Reach and Low Latency
Public cloud providers offer serverless services in multiple
regions, enabling the deployment of applications closer to
end-users for lower latency and improved performance.

39. EXAMPLE SOLUTIONS
41

40. IN YOUR MIND WHAT’S THING BUILD
SERVERLESS
42

41. 3 THINGS SUCCESSOR
We recommend a basic understanding of the following topics:
1. Event-driven architecture
2. Infrastructure as Code (IaC)
3. Serverless technologies
43

42. AWS LAMBDA
S E R V E R L E S S , E V E N T - D R I V E N C O M P U T E
S E R V I C E
44

43. WHAT IS LAMBDA
AWS Lambda is a serverless compute service that runs your code in response to events and automatically manages the underlying
compute resources for you. These events may include changes in state or an update, such as a user placing an item in a shopping
cart on an ecommerce website. You can use AWS Lambda to extend other AWS services with custom logic or create your own
backend services that operate at AWS scale, performance, and security. AWS Lambda automatically runs code in response to
multiple events, such as HTTP requests via Amazon API Gateway, modifications to objects in Amazon Simple Storage Service
(Amazon S3) buckets, table updates in Amazon DynamoDB, and state transitions in AWS Step Functions.
45

44. KEY FEATURE
• Extend other AWS services with custom logic
• Build custom backend services
• Bring your own code
• Completely automated administration
• Built-in fault tolerance
• Package and deploy functions as container images
• Automatic scaling
46
• Connect to relational databases
• Fine-grained control over performance
• Run code in response to Amazon CloudFront requests
• Orchestrate multiple functions
• Integrated security model
• Trust and integrity controls
• Only pay for what you use

45. PROGRAMMING MODEL
• Node.JS
• Python
• Ruby
• Java
• Golang
• C#
• Powershell (?!)
47

46. EXECUTION ENVIRONMENT
The function's runtime communicates with Lambda using the Runtime API. Extensions communicate with Lambda using the
Extensions API. Extensions can also receive log messages and other telemetry from the function by using the Telemetry API.
48

47. EXECUTION ENVIRONMENT LIFECYCLE
Each phase starts with an event that Lambda sends to the runtime and to all registered extensions. The runtime and each extension
indicate completion by sending a Next API request. Lambda freezes the execution environment when the runtime and each
extension have completed and there are no pending events.
49

48. FAILURES DURING THE INVOKE PHASE
If the Lambda function crashes or times out during the Invoke phase, Lambda resets the execution environment. The following
diagram illustrates Lambda execution environment behavior when there's an invoke failure.
50

49. DEPLOYMENT PACKAGES
• Container images
A container image includes the base operating system, the runtime, Lambda extensions, your application code and its
dependencies. You can also add static data, such as machine learning models, into the image.
• ZIP file archives
A .zip file archive includes your application code and its dependencies. When you author functions using the Lambda console or
a toolkit, Lambda automatically creates a .zip file archive of your code.
• Layers
you can use Lambda layers as a distribution mechanism for libraries, custom runtimes, and other function dependencies. Layers
enable you to manage your in-development function code independently from the unchanging code and resources that it uses.
51

50. FUNCTION OVERVIEW
52

51. EXAMPLE PROJECT
See https://github.com/StartloJ/lambda-rds-utils 53

52. SERVERLESS
FRAMEWORK
D E L I V E R S O F T W A R E W I T H R A D I C A L LY L E S S
O V E R H E A D
54

53. SERVERLESS FRAMEWORK CONCEPTS
The Serverless Framework helps you develop and deploy AWS Lambda functions, along with the AWS infrastructure resources
they require. It's a CLI that offers structure, automation and best practices out-of-the-box, allowing you to focus on building
sophisticated, event-driven, serverless architectures, comprised of Functions and Events.
The Serverless Framework is different from other application frameworks because:
• It manages your code as well as your infrastructure.
• It supports multiple languages (Node.js, Python, Java, and more).
Here are the Framework's main concepts and how they pertain to AWS and Lambda.
Ref: https://www.serverless.com/framework/docs
55

54. AWS GO S3 FILE REPLICATOR
56
Ref: https://github.com/serverless/examples/tree/v3/aws-golang-s3-file-replicator

55. AWS NODE TEXT ANALYSIS VIA SNS
57
Ref: https://github.com/serverless/examples/blob/v3/aws-node-text-analysis-via-sns-post-processing/README.md

56. EVENT-DRIVEN
ARCHITECTURE
D E C O U P L E D S Y S T E M S T H AT R U N I N R E S P O N S E
T O E V E N T S
58

57. WHAT IS EVENT-DRIVEN ARCHITECT
An event-driven architecture uses events to trigger and communicate between decoupled services and is common in modern
applications built with microservices. An event is a change in state, or an update, like an item being placed in a shopping cart on an
e-commerce website. Events can either carry the state (the item purchased, its price, and a delivery address) or events can be
identifiers (a notification that an order was shipped).
Event-driven architectures have three key components:
• event producers
• event routers
• event consumers
59

58. HOW IT WORK
60

59. BANKING USE CASE
61

60. INFRASTRUCTURE
AS CODE
T O O L S A L L O W Y O U T O M A N A G E I N F R A S T R U C T U R E
62

61. STANDARDIZE YOUR DEPLOYMENT
WORKFLOW
Providers define individual units of infrastructure, for example compute instances or private networks, as resources. You can
compose resources from different providers into reusable Terraform configurations called modules and manage them with a
consistent language and workflow.
63

62. EXAMPLES
64

63. LIFTING AND
SHIFTING
A W E B A P P L I C AT I O N T O A W S S E R V E R L E S S
65

64. SCENARIOS
Customers migrating to the cloud often want to get the benefits of serverless architecture. But what is the best approach and is it
possible? There are many strategies to do a migration, so lift and shift is often the fastest way to get to production with the
migrated workload.
You might also wonder if it’s possible to lift and shift an existing application that runs in a traditional environment to serverless.
This scenarios shows how to do this for a Mongo, Express, React, and Node.js (MERN) stack web app. However, the discussions
presented in this post apply to other stacks too.
66

65. WHY DO A LIFT AND SHIFT
MIGRATION?
Lift and shift, or sometimes referred to as rehosting the application, is moving the application with as few changes as possible. Lift
and shift migrations often allow you to get the new workload in production as fast as possible. When migrating to serverless, lift
and shift can bring a workload that is not yet in the cloud or in a serverless environment to use managed and serverless services
quickly.
Migrating a non-serverless workload to serverless with lift and shift might not bring all the serverless benefits right away, but it
enables the development team to refactor, using the strangler pattern, the parts of the application that might benefit from what
serverless technologies offer.
67

66. WHY MIGRATE A WEB APP TO
SERVERLESS?
68

67. WHY MIGRATE A WEB APP TO
SERVERLESS?
Web apps hosted in a serverless environment benefit most from the capability of serverless applications to scale automatically and
for paying for what you use.
Imagine that you have a personal web app with little traffic. If you are hosting in a serverless environment, you don’t pay a fixed
price to have the servers up and running. Your web app has only a few requests and the rest of the time is idle.
This benefit applies to the opposite case. For an owner of a small ecommerce site running on a server, imagine if a social media
influencer with millions of followers recommends one of their products. Suddenly, thousands of requests arrive and make the site
unavailable. If the site is hosted on a serverless platform, the application will scale to the traffic that it receives.
69

68. REQUIREMENTS FOR MIGRATION
Before starting a migration, it is important to define the nonfunctional requirements that you need the new application to have.
These requirements help when you must make architectural decisions during the migration process.
These are the nonfunctional requirements of this migration:
• Environment that scales to zero and scales up automatically.
• Pay as little as possible for idle time.
• Configure as little infrastructure as possible.
• Automatic high availability of the application.
• Minimal changes to the original code.
70

69. UI APPLICATION
71

70. APPLICATION OVERVIEW
72
This demo application simulates a swag ecommerce site.
The database layer stores the products, users, and the
purchases history.
The server layer takes care of the ecommerce business logic,
hosting the product images, and user authentication and
authorization.
The web layer takes care of all the user interaction and
communicates with the server layer using REST APIs.

71. MIGRATE TO A SERVERLESS
ENVIRONMENT
73
Database migration: Migrate the database from on-
premises to MongoDB Atlas. Maybe DocumentDB or
DynamoDB
Backend migration: Migrate the NodeJS/Express
application from on-premises to an AWS Lambda function.
Web app migration: Migrate the React web app from on-
premises to AWS Amplify.
Authentication migration: Migrate the custom-built
authentication to use Amazon Cognito.
Storage migration: Migrate the local storage of images to
use Amazon S3 and Amazon CloudFront.

72. DATABASE MIGRATION
To get started, create a new Atlas cluster, then migrate the data from the existing database to the serverless one. To migrate the
data, you can first dump all the content of the database to a dump folder and then restore it to the cloud:
$ mongodump --uri="mongodb://<localuser>:<localpassword>@localhost:27017"
$ mongorestore --uri="mongodb+srv://<user>:<password>@<clustername>.debkm.mongodb.net" .
74

73. BACKEND MIGRATION
One option for this migration is to use AWS Fargate. Fargate is a serverless container service that allows you to scale automatically,
and you pay as you go. Another option is to use AWS AppRunner, a container service that auto scales and you also pay as you go.
However, neither of these options align with our migration requirements, as they don’t scale to zero.
Another option for the lift and shift migration of this Node.js application is to use Lambda with the AWS Lambda Web Adapter.
The AWS Lambda Web Adapter is an open-source project that allows you to build web applications with familiar frameworks, like
Express.js, Flask, SpringBoot, and run it on Lambda. You can learn more about this project in its GitHub repository.
Ref: https://github.com/awslabs/aws-lambda-web-adapter
75

74. WEB APP MIGRATION
The final layer to migrate is the React application. The best way to migrate the web layer and to adhere to the migration
requirements is to use AWS Amplify to host it. AWS Amplify is a fully managed service that provides many features like hosting web
applications and managing the CICD process for the web app. It provides client libraries to connect to different AWS resources, and
many other features.
Migrating the React application is as simple as creating a new Amplify application in your AWS account and uploading the React
application to a code repository like GitHub. This AWS Amplify application is connected to a GitHub branch, and when there is a
new commit in this branch, AWS Amplify redeploys the code.
76

75. WHAT’S PROBLEM FOR THIS SOLUTION
77

76. THE ENTERPRISE USE SERVERLESS
78

77. THE ENTERPRISE USE SERVERLESS
79

78. BREAK!
80

79. CHALLENGING
W H Y S O H A R D T R A N S F O R M
Overall, the challenges and considerations for
cloud adoption in Thailand are similar to the
challenges and considerations for cloud
adoption in other countries.
81

80. DATA PRIVACY AND COMPLIANCE
DATA SOVEREIGNTY
Thailand has strict data sovereignty laws that require personal data
of Thai citizens to be stored within the country. This can complicate
the use of global cloud providers.
PERSONAL DATA PROTECTION ACT
Compliance with Thailand's PDPA is crucial. Organizations need to
ensure data privacy, consent management, and security measures
are in place.
82

81. INTERNET CONNECTIVITY AND
INFRASTRUCTURE
RELIABLE INTERNET
The quality and reliability of internet connections can vary,
particularly in rural areas. Organizations must ensure they have
sufficient bandwidth and backup plans in place.
LATENCY
High latency can impact the performance of applications hosted on
cloud servers located outside Thailand.
83

82. SECURITY CONCERNS
DATA SECURITY
Security is a top concern, and organizations need to implement
robust security measures to protect data from cyber threats and
breaches.
CLOUD SECURITY
Understand the shared responsibility model of cloud providers and
ensure that security measures are in place on both the provider and
user sides.
84

83. THE CHANGE WILL BE RESISTANCE
CULTURAL CHANGE
Cloud adoption often requires a cultural shift within the organization
to adapt to new ways of working and managing IT resources.
COMPLIANT AND CONTRACTUAL
Review contracts with cloud providers carefully to understand
service-level agreements (SLAs), responsibilities, and exit strategies.
85

84. COST OF CLOUD ADOPTION
The cost of cloud adoption can be a barrier for some businesses in Thailand. However, it is important to note that cloud adoption
can save businesses money in the long run by reducing IT costs and improving efficiency.
While cloud can offer cost savings, it's important to manage costs effectively. Cloud usage should be optimized to avoid unexpected
expenses.
86

85. LACK OF SKILLED CLOUD
PROFESSIONALS
There is a shortage of skilled cloud professionals
in Thailand. This can make it difficult for
businesses to find the expertise they need to
implement and manage their cloud deployments.
87

86. BREAK!
88

87. STUDY CASE REAL WORLD
C O M PA N I E S H A V E A P P L I E D
S E R V E R L E S S A R C H I T E C T U R E S
89

88. IOT BACKENDS
90
Ref: https://github.com/aws-samples/lambda-refarch-iotbackend

89. DATA PROCESSING
91

90. IT AUTOMATION
92

91. LEARNING
PATH
93

92. CLOUD ENGINEERING
C LO U D CO M P U T I N G F U N DA M E N TA L S
Start with a solid understanding of cloud computing concepts
BA S I C C LO U D S E RV I C ES
Familiarize yourself with core cloud services like virtual machines,
storage, databases, and networking
S E RV E R L ES S BA S I C S
Fundamentals of serverless computing, including what it is, how it works,
and its advantages over traditional computing models.
S E RV E R L ES S F R A M E WO R KS
Explore serverless frameworks like the Serverless Framework, AWS
Serverless Application Model (SAM), and Azure Functions
94

93. DEVELOPMENT
P RO G R A M M I N G L A N G UAG ES
Gain proficiency in programming languages commonly used for serverless
development, such as JavaScript (Node.js), Python, Go, or C#.
E V E N T - D R I V E N A R C H I T EC T U R E
Understand the principles of event-driven architecture, which is
fundamental for serverless applications.
A P I D ES I G N A N D M I C RO S E RV I C ES
Familiarize yourself with microservices architecture and API design, which
often align with serverless development practices.
S C A L A B I L I T Y & P E R F O R M A N C E O P T I M I Z AT I O N
Designing serverless functions for high scalability and optimizing
performance for handling traffic spikes.
95

94. DEVSECOPS AND SRE
S EC U R I T Y A N D CO M P L I A N C E
Master serverless-specific security practices, including encryption, access
control, and handling sensitive data.
C I / C D A N D D E VO P S
Continuous integration and continuous deployment practices and tools, as well
as DevOps principles, to automate serverless application deployments.
M O N I TO R I N G A N D D E B U G G I N G
Gain expertise in setting up monitoring, logging, and debugging solutions
tailored to serverless architectures
CO S T M A N AG E M E N T
Understanding pricing models, monitoring resource consumption, and
implementing cost-efficient practices.
96

95. PM AND PO
CO L L A B O R AT I O N A N D CO M M U N I C AT I O N
Strengthen communication and collaboration skills to work effectively with cross-
functional teams, including developers, operations, and business stakeholders.
P ROJ EC T M A N AG E M E N T
Acquire project management skills for planning and executing serverless
projects with clear objectives, timelines, and deliverables.
V E N D O R - AG N O S T I C K N OW L E D G E
While gaining expertise in understand serverless principles that can be
applied across various providers for flexibility and avoiding vendor lock-in.
S O F T S K I L L S
Cultivate problem-solving, adaptability, and the ability to learn and adapt
to new technologies and methodologies quickly.
97

96. CONCLUSION
G A M E A N D C O N C L U S I O N
98

97. KAHOOT
99
https://create.kahoot.it/share/serverless-adoption/0243f611-f478-49ee-83e0-6caf8d13deec

98. CONCLUSION
100

99. MY CONTACT
@ WATC H A R I N _ YA N h t t p s : / / g i t h u b . c o m / S t a r t l o J Wa t c h a r i n Ya n g - N ga m
P I N G M E F O R YO U R Q U E S T I O N