In this talk we will take an "regular" solution and turn it into cloud solution, we will also see a bit code example in NODE.js

1. AWS introduction
Michael Haberman
Freelancer

2. What we are going to do?
An application Scenario
Before cloud solution
How cloud can help us?

3. Every cloud talk must start
with
Why use cloud?

4. Before cloud solutions

5. Registration system
We offer registration infrastructure
That must be highly scalable
The infrastructure has very high load picks

6. Registration system
Flow:
user authenticates
user send a registration request (once an hour)
application saves it
someone manually accept / reject the request
email is sent
in case of accept - allow print of confirmation (auto generated
image)

7. Solution Architecture
Clients
Web
Service
Scale?

8. Solution Architecture
Clients
Web
Service
Web
Service
How to
balance the
load?

9. Solution Architecture
Clients
Web
Service
Web
Service
How to
continue
scaling?
Load balancer
What
happens
when the
service is
over loading?

10. Solution Architecture
Clients
Web
Service
Web
Service
Which
machine?
Queue
Who should
send emails?
DB?

11. Solution Architecture
Clients
Web
Service
Web
Service
Queue
DB
Single
DB?
Which
machin
e?
Maybe we
need
some
cache?
Where to
store the
images?

12. Registration system
New requirement:
support Mobile push notification

13. How does cloud help us?

14. Features
Compute
Storage
Databases
Networking
Mobile support (SNS)
Security
Application Services
(Queue, emails, etc…)
Developer Tools (Git, CI)
Management Tools
Analytics
Enterprise Applications

15. Let’s see the AWS Console

16. Cloud Solution
Clients
Web
Service
Web
Service
Queue
DB
Open Issues:
DB (replication)
Push notification
Images
Cache
Send Emails

17. Choosing Database(SQL)
First thought:
EC2 - with a DB Instance
What benefit do we gain by using a cloud base
server with DB Instance on it?

18. Choosing Database(SQL)
EC2 - might not be the first choose for DB
You pay for compute, storage, ram and etc…
Storage is expensive
You have to maintain the DB
Taking responsibility on backups
You have an entire machine only to get a connection
string

19. Choosing Database(SQL)
RDS - Rational Database Services
All you get is a connection string
Auto maintenance
Auto backups
Replication support
Paying for storage (only what you use vs EC2)
Auto address swap in case of failure

20. DynamoDB
Solution for noSQL databases

21. Cloud Solution
Clients
Web
Service
Web
Service
Queue
RDS
Open Issues:
DB (replication)
Push notification
Images
Cache
Send Emails
Auto
Scale?
Load
balance
?

22. EC2 - Auto Scale
Define a threshold using CloudWatch
Add instance when event occur
Remove instance when event occur
Define min/max/desired amount of instances
Register for notification (load tests…)

23. EC2 - Load Balancer
The Auto Scale will create instances upon high loads
The Load Balancer will keep an equal load in the
instances
very easy to define

24. Cloud Solution
Clients
EC2 EC2
Queue
RDS
Open Issues:
DB (replication)
Push notification
Images
Cache
Send Emails
Load Balancer + Auto
Scale

25. ElasticCache
Few EC2 instance may require high speed data
sharing
Distributed cache would solve that
A key value pair
Expiration is supported (once an hour)
When new instance is created - state is easily
preserved

26. ElasticCache
var params = {
ResourceName: 'STRING_VALUE', /* required */
Tags: [ /* required */
{
Key: 'STRING_VALUE',
Value: 'STRING_VALUE'
},]};
elasticache.addTagsToResource(params, function(err, data) {
});

27. Cloud Solution
Clients
EC2 EC2
Queue
RDS
Open Issues:
DB (replication)
Push notification
Images
Cache
Send Emails
Load Balancer + Auto
Scale
Cloud
Front

28. SQS - Simple Queue
Service
Pay as you go
No need for dedicated machine
Simple API
Dead letter queue support

29. SQS - Enqueue
var params = {
MessageBody: 'STRING_VALUE', /* required */
QueueUrl: 'STRING_VALUE', /* required */
MessageAttributes: {
someKey: {
DataType: 'STRING_VALUE', /* required */
StringValue: 'STRING_VALUE'
},}} ;
sqs.sendMessage(params, function(err, data) {
});

30. SQS - Dequeue
var params = {
QueueUrl: 'STRING_VALUE', /* required */
NumberOfMessages: 0,
VisibilityTimeout: 0,
WaitTimeSeconds: 0
};
sqs.receiveMessage(params, function(err, data) {
});

31. Security!

32. Cloud Solution
Clients
EC2 EC2
SQS
RDS
Open Issues:
DB (replication)
Push notification
Images
Cache
Send Emails
Load Balancer + Auto
Scale
Cloud
Front

33. Cloud Storage Solutions
EC2
high cost
better performance when in the same machine
S3
low cost
distributed between different services
Glacier
low performance - archive
Which one would you use?

34. S3
S3
Separated into buckets
Each item can be up to 5 terabyte
Support event notification (upon item add send
email)
Encryption support

35. S3 - SDK
var params = {
Bucket: 'STRING_VALUE', /* required */
Key: 'STRING_VALUE', /* required */
Body: new Buffer('...') || 'STRING_VALUE' || streamObject,
Expires: new Date || 'Wed Dec 31 1969 16:00:00 GMT-0800 (PST)' || 123456789,
Metadata: {
someKey: 'STRING_VALUE',
}};
s3.putObject(params, function(err, data) {
});

36. Cloud Solution
Clients
EC2 EC2
SQS
RDS
Open Issues:
DB (replication)
Push notification
Images
Cache
Send Emails
Load Balancer + Auto
Scale
Cloud
Front
S3

37. Event notification
S3
upon change use SNS, SQS, Lambda events
in our example, send an email. How?

38. Lamba events
S3
upon change use SNS, SQS, Lambda events
in our example, send an email. How?

39. Cloud Solution
Clients
EC2 EC2
SQS
RDS
Open Issues:
DB (replication)
Push notification
Images
Cache
Send Emails
Load Balancer + Auto
Scale
Cloud
Front
S3
Lambd
aSES
SNS

40. AWS - endless feature
GIT
Deployment
CDN
Monitoring
Analytics

41. Questions?

42. Contact Me
Website: www.haberman.io
Email: michael@haberman.io
Twitter: @hab_mic
Blog: http://blogs.microsoft.co.il/michaelh/