Why go serverless?

You don't have to spend time administrating your servers.
No servers to manage? Serverless

  1. Managed compute, no need to guess CPU / Memory requirements
  2. Do not pay for idle resources - Scales to zero
  3. Improved security - Temporary/Ephemeral runtime
  4. Reduce costs - pay per millisecond of execution time, not per hour!
  5. Monitoring / logging / alerts integrated - Reduce operational complexity
  6. Automatically scales as needed - can handle any spike on load
  7. Reliable - leverage the public Cloud, the network and capability
  8. Deliver to your customers - facilitates iterations as quick as two seconds per deployment and even quicker to roll back
AWS certified

Serverless engineering service

Addressing pain points like:

Connect on LinkedIn, view my CV, watch my presentations and my videos on Serverless.

AWS service counts around the world

Rank Region name Service count
1 us-east-1 232
2 us-west-2 219
3 eu-west-1 208
4 ap-southeast-2 201
5 ap-northeast-1 200
6 eu-central-1 198
7 ap-southeast-1 187
8 eu-west-2 182
9 us-east-2 178
10 ap-northeast-2 172
11 ap-south-1 160
12 ca-central-1 158
13 eu-north-1 141
14 sa-east-1 137
15 us-west-1 137
16 eu-west-3 135
17 us-gov-west-1 132
18 ap-east-1 112
19 me-south-1 109
20 cn-north-1 104
21 af-south-1 103
22 cn-northwest-1 102
23 eu-south-1 100
24 us-gov-east-1 100
25 ap-northeast-3 92
26 ap-southeast-3 59
27 us-iso-east-1 58
28 us-isob-east-1 43
29 us-iso-west-1 30

Estimating serverless costs of this demo

Assuming an execution time of 100ms or less on minimum 128 lambda as this demo is configured and ignoring Free Tier.

Lambda: $0.20 per 1 million requests = ${ requestcost }

Lambda: $0.000000208 per <= 100 ms request duration = ${ durationcost.toFixed(2) }

API Gateway: $4.25 per million = ${ gwcost }

Outbound Data Transfer Costs: $0.12/GB = ${ outboundcost }

Total: ${ total } USD

Contact form