Slide presentasi ini dibuat oleh Petra Novandi Barus sebagai pemateri di acara Dapur Startup Bandung Developer Day pada 29 Juli 2016 di Dicoding Space Bandung

1. SERVERLESS ARCHITECTURE
Petra Novandi Barus
Chief Technology Officer
UrbanIndo.com

2. WHO AM I?
Petra Novandi Barus
2011- CTO UrbanIndo.com
2009 Magister Informatics ITB
2005 Informatics Engineering ITB
petrabarus.net
petra.barus@gmail.com
@petrabarus
askfm.com/petrabarus

3. WHAT AM I GOING TO TALK ABOUT?
Function as a Service (Serverless)
Why?
Pros and Cons
Use Cases

4. TYPES OF DEPLOYMENT HOSTS
Physical Host
Virtual Private Server
Docker
Function as a Service

5. FUNCTION AS A SERVICE
Function is a unit of deployment
Execute only when need
No server maintainance

6. VENDORS

7. COMPARISON
ACF GCF Lambda
Status Preview Alpha Production
Programming Language JS, C#, F#, Python, PHP,
Bash, Powershell
Javascript Java, Javascript, Python
Event Source Stream Analytics,
OneDrive, BlobStorage
PubSub, Google Storage
event
S3, SES, DynamoDB,
Kinesis, CloudWatch
HTTP WebHook HTTP Triger API Gateway

8. FEATURES
Run code without server
 Just upload the code and run
Only pay what you need
 No wasted CPU usage
Event driven model
 Can handle event sent from other component
Programming Languages Support
 Java, Python, Javascript, etc...

9. PROS
Reduced Development Cost
Only develop what is needed
Reduced Operational Cost
Reduced manpower for managing servers
Automatic Scaling
Will adjust the number of requests

10. PROS
Easier Deployment
Packaging, startup scripts, env setting
Easier Monitoring
Vendor provide monitoring like time, bandwidth,
#request
Easier Unit Testing
Only test the function

11. CONS
Vendor Lock
Hard to switch vendor (for now)
Multitenancy Problem
Share machine with other client
Configuration
Hard to configure the CPU, memory, etc

12. CONS
Vendor Control
Have to adjust with updates from vendor
Server Optimization
Cannot optimize server, only in code
Integration Testing
Has to rely testing in the cloud instead of own server

13. CONS
Security
Very fined-grained security management
Source Code Management
Build and upload changed function (JAR/ZIP)

14. USE CASE
TEST EMAILS STORAGE

15. USE CASE
HADOOP TO DYNAMODB

16. USE CASE
IMAGE RESIZING & ANALYSIS

17. USE CASE
DYNAMIC WEBSITE

18. USE CASE
OTHERS
Automation
Cron Task
Bots
Internet of Things
Mobile Backend

19. ADVICES
There are always shiny new things
Always use the technologies you
are comfortable with
Try learning new technologies to prepare
when you need

20. THANK YOU!