Dengan cloud computing, Anda akan mendapatkan sejumlah keuntungan, seperti kemampuan untuk scale web application atau website secara on-demand. Jika Anda sedang membangun web application dan ingin mulai menggunakan cloud computing, mungkin terlintas di benak Anda, “Mulai dari mana?” Mari bergabung bersama kami dalam sesi ini untuk memahami praktik terbaik untuk scaling infrastruktur Anda, mulai dari nol hingga jutaan pengguna. Kami akan tunjukkan cara terbaik untuk membangun bisnis Anda dengan layanan AWS, membantu memutuskan pilihan yang lebih cerdas, dan bagaimana scaling infrastruktur Anda di cloud.

1. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Build a Website on AWS for
Your First 10 Million Users

2. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Silvia Wibowo
Solutions Architect
Silvia has been in Amazon for 1.5 years as a
Solutions Architect. Business as usual means
discussing with customers about IT architecture
and how to optimize in areas such as security,
reliability, performance, cost optimization, and
operational excellence.
Today’s Speaker

3. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.© 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Build a Website on AWS for Your First
10 Million Users11

4. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.© 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Who are you?

5. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
http://i.telegraph.co.uk/multimedia/archive/02674/CLIMBER_2674482b.jpg

6. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.

7. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Now that’s a lot
of things to read!
This is NOT
where we
want to start!

8. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
It’s not the single thing that
fixes everything.

9. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
What do we need first?

10. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Some basics…

11. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
AWS Global Infrastructure
Region, # of zones
Coming Soon!

12. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
AWS Global Infrastructure
100+ Edge
Locations

13. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
ENTERPRISE
APPS
DEVELOPMENT & OPERATIONSMOBILE SERVICESAPP SERVICESANALYTICS
Data
Warehousing
Hadoop/
Spark
Streaming Data
Collection
Machine
Learning
Elastic
Search
Virtual
Desktops
Sharing &
Collaboration
Corporate
Email
Backup
Queuing &
Notifications
Workflow
Search
Email
Transcoding
One-click App
Deployment
Identity
Sync
Single Integrated
Console
Push
Notifications
DevOps Resource
Management
Application Lifecycle
Management
Containers
Triggers
Resource
Templates
TECHNICAL &
BUSINESS
SUPPORT
Account
Management
Support
Professional
Services
Training &
Certification
Security
& Pricing
Reports
Partner
Ecosystem
Solutions
Architects
MARKETPLACE
Business
Apps
Business
Intelligence
DatabasesDevOps
Tools
NetworkingSecurity Storage
Regions
Availability
Zones
Points of
Presence
INFRASTRUCTURE
CORE SERVICES
Compute
VMs, Auto-scaling,
& Load Balancing
Storage
Object, Blocks,
Archival, Import/Export
Databases
Relational, NoSQL,
Caching, Migration
Networking
VPC, DX, DNS
CDN
Access
Control
Identity
Management
Key
Management
& Storage
Monitoring
& Logs
Assessment
and reporting
Resource &
Usage Auditing
SECURITY & COMPLIANCE
Configuration
Compliance
Web application
firewall
HYBRID
ARCHITECTURE
Data
Backups
Integrated
App
Deployments
Direct
Connect
Identity
Federation
Integrated
Resource
Management
Integrated
Networking
API
Gateway
IoT
Rules
Engine
Device
Shadows
Device
SDKs
Registry
Device
Gateway
Streaming Data
Analysis
Business
Intelligence
Mobile
Analytics

14. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
So let’s start from…

15. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
You

16. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
1 User
Amazon
EC2
instance
Elastic IP
User
Amazon
Route 53

17. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
“We’re gonna need a bigger box”
• Simplest approach
• Can now leverage PIOPS
• High I/O instances
• High memory instances
• High CPU instances
• High storage instances
• Easy to change instance sizes
• Will hit an endpoint eventually
c4.8xlarge
m4.2xlarge
t2.micro

18. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
“We’re gonna need a bigger box”
• Simplest approach
• Can now leverage PIOPS
• High I/O instances
• High memory instances
• High CPU instances
• High storage instances
• Easy to change instance sizes
• Will hit an endpoint eventually
c4.8xlarge
m4.2xlarge
t2.micro

19. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
1 User
• No failover
• No redundancy
• Too many eggs in one
basket
EC2
Instance
Elastic IP
User
Amazon
Route 53

20. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Users >1

21. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Users > 1
Web
Instance
Database
Instance
Elastic IP
User
Amazon
Route 53

22. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Self-managed Fully managed
Amazon EC2 Amazon
DynamoDB
Amazon RDS Amazon
Redshift
Database options

23. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
• MySQL or Postgres compatible
• Automatic storage scaling (up to 64 TB)
• Up to 15 read-replicas
• Continuous (incremental) backups to
Amazon S3
• 6-way replication across 3 zones
Amazon Aurora

24. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
To NoSQL, or not to NoSQL?

25. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Start with SQL databases

26. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Why start with SQL?
• Established and well-worn technology.
• Lots of existing code, communities, books, and tools.
• You aren’t going to break SQL DBs in your first millions
of users. No, really, you won’t.*
• Clear patterns to scalability.
*Unless you are doing something SUPER peculiar with the data or you have MASSIVE amounts of it.
…but even then SQL will have a place in your stack.

27. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
> 5 TB in year one?
Incredibly data intensive workload?
OK!
You might need NoSQL.

28. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Why else might you need NoSQL?
• Super low-latency applications
• Highly nonrelational data
• Need schema-less data constructs*
• Rapid ingest of data (thousands of records/sec)
• Massive amounts of data (again, in the TB range)
*Need!= “It’s easier to do dev without schemas”

29. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Users >100

30. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Users >100
Web
instance
Elastic IP
RDS DB
instance
User
Amazon
Route 53

31. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Users >1000

32. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Users >1000
Web
Instance
RDS DB Instance
Active (Multi-AZ)
Availability Zone Availability Zone
Web
Instance
RDS DB Instance
Standby (Multi-AZ)
Load
balancer
User
Amazon
Route 53

33. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Elastic Load Balancing
• Highly available
• TCP/{1 – 65535}
• Health checks
• Session stickiness
• Monitoring / logging
• Secure sockets layer

34. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Application Load Balancer
• Highly available
• TCP/{1 – 65535}
• Health checks
• Session stickiness
• Monitoring / logging
• Content-based routing
• Container-based apps
• WebSockets
• HTTP/2

35. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
horizontally
vertically

36. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Indonesia Customer

37. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Users >100,000

38. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Users > 10,000s–100,000s
RDS DB Instance
Active (Multi-AZ)
Availability Zone Availability Zone
RDS DB Instance
Standby (Multi-AZ)
Load
balancer
RDS DB Instance
Read Replica
RDS DB Instance
Read Replica
RDS DB Instance
Read Replica
RDS DB Instance
Read Replica
Web
Instance
Web
Instance
Web
Instance
Web
Instance
Web
Instance
Web
Instance
Web
Instance
Web
Instance
Amazon
Route 53User

39. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
What about
performance and efficiency?

40. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
RDS DB Instance
Active (Multi-AZ)
Availability Zone
Load
balancer
Amazon S3
Amazon
CloudFront
Amazon
Route 53
User
Shift some load around
Web Instances
Availability Zone
Web Instances
RDS DB Instance
Standby (Multi-AZ)

41. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Load
balancer
Amazon S3
Amazon
CloudFront
Amazon
Route 53
User
Shift some load around
Availability Zone
Web Instances
RDS DB Instance
Standby (Multi-AZ)

42. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
• Object-based storage
• Highly durable
• Great for static assets
• “Infinitely scalable”
• Objects up to 5 TB in
size
• Optional encryption
Amazon Simple Storage Service (S3)

43. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Cache content for faster delivery
• Lower load on origin
• Dynamic and static content
• Low TTLs (as short as 0
seconds)
• Streaming video
• Custom SSL certificates
• Optimized for AWS
Amazon CloudFront

44. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Amazon CloudFront
ResponseTime
ServerLoad
Response
Time
Server
Load
Response
Time
Server
Load
No CDN CDN for Static
Content
CDN for Static &
Dynamic Content
0
20
40
60
80
12:00AM
12:00AM
12:00AM
12:00AM
12:00AM
12:00AM
12:00AM
12:00AM
12:00AM
12:00AM
12:00AM
12:00AM
12:00AM
12:00AM
VolumeofData
Delivered(Gbps)

45. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Indonesia Customer

46. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Shift some load around
RDS DB Instance
Active (Multi-AZ)
Availability Zone
Load
balancer
Amazon S3
Amazon
CloudFrontUser
ElastiCache DynamoDB
Web Instances
Amazon
Route 53

47. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Amazon DynamoDB
• Managed NoSQL database
• Provisioned throughput
• Fast, predictable performance
• Fully distributed, fault tolerant
• JSON support
• Items up to 400 KB

48. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Amazon ElastiCache
• Managed Memcached or Redis
• Scale from one to many nodes
• Self-healing (replaces dead instance)
• Single digit ms speeds (usually)
• Local to a single AZ for Memcache
• Multi-AZ possible with Redis

49. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Shift some load around
RDS DB Instance
Active (Multi-AZ)
Availability Zone
Load
balancer
Amazon S3
Amazon
CloudFront
Amazon
Route 53
User
ElastiCache DynamoDB
Web Instances

50. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Now that our web tier is
much more lightweight,
we can revisit the beginning
of our talk…

51. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Auto Scaling!

52. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Automatic resizing of compute clusters
Define min/max pool sizes
CloudWatch metrics drive scaling
On-Demand or Spot Instances
aws autoscaling create-auto-scaling-group
--auto-scaling-group-name MyGroup
--launch-configuration-name MyConfig
--min-size 4
--max-size 200
--availability-zones us-west-2c, us-west-2b
Auto Scaling

53. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Sunday Monday Tuesday Wednesday Thursday Friday Saturday
Typical weekly traffic to Amazon.com

54. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Sunday Monday Tuesday Wednesday Thursday Friday Saturday
Typical weekly traffic to Amazon.com
Provisioned capacity

55. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
November
November traffic to Amazon.com

56. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Provisioned capacity
November
November traffic to Amazon.com

57. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
November traffic to Amazon.com
76%
24%
November
Provisioned capacity

58. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
November traffic to Amazon.com
November

59. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Auto Scaling
lets you do this!

60. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Users > 500,000+
Availability Zone
Amazon
Route 53
User
Amazon S3
Amazon
CloudFront
Availability Zone
Load
balancer
DynamoDB
RDS DB Instance
Read Replica
Web
Instance
Web
Instance
Web
Instance
ElastiCache RDS DB Instance
Read Replica
Web
Instance
Web
Instance
Web
Instance
ElastiCacheRDS DB Instance
Standby (Multi-AZ)
RDS DB Instance
Active (Multi-AZ)

61. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Users > 500,000+
Availability Zone
Amazon
Route 53
User
Amazon S3
Amazon
CloudFront
Availability Zone
Load
balancer
DynamoDB
RDS DB Instance
Read Replica
Web
Instance
Web
Instance
Web
Instance
ElastiCache RDS DB Instance
Read Replica
Web
Instance
Web
Instance
Web
Instance
ElastiCacheRDS DB Instance
Standby (Multi-AZ)
RDS DB Instance
Active (Multi-AZ)

62. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Use automation

63. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Whoa!

64. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
AWS application management solutions
Convenience Control
Higher-level services Do it yourself
AWS
Elastic Beanstalk
AWS
OpsWorks
AWS
CloudFormation
Amazon EC2

65. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
AWS CodeDeploy
• Deploys your code to a “fleet” of EC2 instances
• 1 – 10,000s of instances
• Automatically schedules updates (multiple zones)
• Application and Deployment groups described in
YAML-formatted files
• Can reference Auto Scaling groups
• AWS Management Console, CLI, or APIs
• Can be used with Chef recipes or Puppet scripts

66. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Users >500,000+
• Monitoring, metrics, and logging
• If you can’t build it internally,
outsource it! (third-party SaaS)
• What are customers saying?
• Try to squeeze as much performance
out of each service/component

67. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
AGGREGATE
LEVEL
METRICS
LOG
ANALYSIS
EXTERNAL
SITE
PERFORMANCE
HOST
LEVEL
METRICS

68. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
There are further
improvements to be made in
breaking apart our
web/app layer

69. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
SOA
What does this mean?

70. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.

71. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Now that’s a lot
of things to read!
This is NOT
where we
want to start!

72. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
This is NOT
where we
want to start!
This IS where
we want to start!
Now that’s a lot
of things to read!

73. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
SOAing
Move services into their own tiers
• Treat them separately
• Scale them independently
It offers flexibility and greater
understanding of each component

74. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Loose coupling + SOA = winning
DON’T REINVENT THE WHEEL
• Email
• Queuing
• Transcoding
• Search
• Databases
• Monitoring
• Metrics
• Logging
• Compute
Amazon
CloudSearch
Amazon SQSAmazon SNS
Amazon Elastic
Transcoder
Amazon SWFAmazon SES
AWS Lambda

75. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
• Reliable (Multi-AZ)
• Scalable (unlimited messages)
• Secure (queue authentication)
• Simple (simple APIs)
Application Services – Amazon SQS
SQS
messages
Get
message
Instance
Put
message
Instance
Amazon SNS Topic
Publish
notification
Queue is subscribed
to topic

76. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Compute / Platform – AWS Lambda
• Functions triggered by events
• JavaScript, Java, Python, and C#
• Managed
• Implicit scaling
S3 bucket
Lambda
Push: event
notification
DynamoDB
Pull: DynamoDB
Stream
Amazon
Kinesis
Pull:
Amazon Kinesis
stream

77. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Loose coupling sets you free!
The looser they're coupled, the bigger they scale
• Independent components
• Design everything as a black box
• Decouple interactions
• Favor services with built-in redundancy and scalability
• Don’t build your own!
S3 bucket
Lambda
Push: event
notification
DynamoDB
Pull: DynamoDB
Stream
Amazon
Kinesis
SQS
messages
Get
message
Instance
Put
message
Instance
Amazon SNS Topic
Publish
notification
Queue is subscribed
to topic
Pull:
Amazon Kinesis
stream

78. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Users >1,000,000

79. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Users >1 million+
Reaching a million and above is going to require some bit
of all the previous things:
• Multi-AZ
• Elastic Load Balancing between tiers
• Auto Scaling
• Service oriented architecture (SOA)
• Serving content smartly (Amazon S3/CloudFront)
• Caching off DB
• Moving state off tiers that auto scale

80. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Users >1 million+
RDS DB Instance
Active (Multi-AZ)
Availability Zone
Load
balancer
RDS DB Instance
Read Replica
RDS DB Instance
Read Replica
Web
Instance
Web
Instance
Web
Instance
Web
Instance
Amazon
Route 53
User
Amazon S3
Amazon
CloudFront
DynamoDB
Amazon SQS
ElastiCache
Worker
Instance
Worker
Instance
Amazon
CloudWatch
Internal App
Instance
Internal App
Instance Amazon SES
Lambda

81. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Global Customer

82. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
The next big steps

83. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Users >5 million - 10 million
Database Issues?
How can you solve it?
• Federation—splitting into multiple DBs based on function
• Sharding—splitting one dataset up across multiple hosts
• Moving some functionality to other types of DBs (NoSQL, Graph)

84. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Database federation
• Split up databases by function/purpose
• Harder to do cross-function queries
• Essentially delays sharding/NoSQL
• Won’t help with single huge functions/tables
Forums DB
Users DB
Products
DB

85. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Sharded horizontal scaling
• More complex at the application layer
• No practical limit on scalability
• Operation complexity/sophistication
• Shard by function or key space
• RDBMS or NoSQL
User ShardID
002345 A
002346 B
002347 C
002348 B
002349 A
CBA

86. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Shifting functionality to NoSQL
• Similar in a sense to federation
• NoSQL vs. SQL
• Leverage managed services like
DynamoDB
Some use cases:
• Leaderboards/scoring
• Rapid ingest of clickstream/log data
• Temporary data needs (cart data)
• “Hot” tables
• Metadata/lookup tables
DynamoDB

87. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
A quick review

88. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
A quick review
• Multi-AZ your infrastructure.
• Make use of self-scaling services—ELB, Amazon S3,
Amazon SNS, Amazon SQS, Amazon SWF, Amazon SES, etc.
• Built-in redundancy at every level
• Start with what you know: SQL/NoSQL
• Cache data both inside and outside your infrastructure.
• Use automation tools in your infrastructure.

89. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
A quick review continued
• Make sure you have good metrics/monitoring/logging
• Split tiers into individual services (SOA)
• Use Auto Scaling once you’re ready for it
• Don’t reinvent the wheel
• Move to NoSQL if and when it makes sense

90. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Web and Mobile Application for
11 Million Users

91. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.© 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Thank You