SERVERLESS
Use cases & Experience
Artem Arkhipov, Web Lead
Road to serverless
Our projects in 2016
Setup community & attend events
Official partners
Serverless in our projects today
CAT 1
CAT 2
CAT 3
Image processing
C1: Some functionality
Image resizing on flight
C1: Some functionality
There are so many secondary computing jobs on your project.
And you definitely wouldn't like those jobs to create additional load on your main servers.
Start from them!
C2: Significant part
Feature: diagram images
C2: Significant part
Feature: Changelogs
C2: Significant part
Making screenshots
Less 10$ for 160 000 images
2-3 seconds execution time
You save a lot with AWS Lambda functions
Few words about burst auto-scaling
50 users online
500 users online
Probably the load to your service is unstable and hard to predict
Maybe your service requires a parallel computation
Serverless would be
a good deal for you
C3: Fully serverless
Marketing tool
Old system:
Old system:
- Extremely slow, too much data & calculations
- Hard to make updates and scale
- Overpriced as for 90% idle time
New approach:
- Store precalculated data
- Split logic into independent pieces per chart
- Use serverless and don't pay for idle time
Independent pieces
Chart
Ready data
Big Dataset
Recurrent job
C3: Fully serverless
Serverless allows you to make and deploy changes without additional risks to the rest parts of your app
Serverless allows developers to think more about the code and less about the infrastructure
Serverless is not about cost only
RnD & Prototyping
I am interested, what to do next?
- Grab a beer or two
- Think about what you have heard here
- Evaluate your current or future projects from the serverless perspective
- Google and learn more
Or just find a reliable partners and let them do everything for you (except drinking a beer)
;)
- Make your team and yourself happy with serverless!
Thank you!
Artem Arkhipov
ar.arkhipov@gmail.com
skype: tamango92
artem.arkhipov@techmagic.co
github: ar-arkhipov
twitter: ar_arkhipov