To be or not to be Serverless

To Be or not To Be Serverless
14 Septembre 2017

IPPON
EN QUELQUES MOTS
Ippon Technologies 2017

Ippon est un cabinet de conseil et d’expertise en
développement de logiciels innovants
Aurélien SCHWARTZ
Responsable de projet de Data Science chez EDF
“ En nous adressant à Ippon nous cherchions une société capable de nous accompagner dans la construction d’un produit qui n’existait
alors qu’au stade de proof of concept sur nos machines de chercheurs. “

IPPON EN QUELQUES MOTS
15ans
2002 - 2017
30M€
prévisionnel 2017
300collaborateurs
24M€
CA 2016
4continents

NOTRE VISION

Entraînement intensif avec
pour objectif de dépasser nos
limites en équipe
Fondé par Stéphane Nomis, ancien
sportif de haut niveau.
Remise en question
permanente afin de viser
l’excellence
NOS VALEURS
LES VALEURS DU SPORT DE HAUT NIVEAU
APPLIQUÉES AU MANAGEMENT D’UNE ENTREPRISE

Discovery To Delivery
Innover et optimiser votre Time To Market
Une méthode
Agile
Approche
customer/user centric
Accompagnement
et co-construction
Vision claire
et partagée
de votre
stratégie digitale
Des Data
valorisées
Développement
de logiciel
industrialisé
Des infrastructures
bien managées

NOS SERVICES

NOS SERVICES
Stratégie Client
Architecture IT
Transition Agile
Vision Produit
Management
CONSEIL
Design thinking
Ergonomie
Expérience Utilisateur
UI
Design intéractif
EXPÉRIENCE
UTILISATEUR
& DESIGN FullStack
Java, JavaScript & JVM
OpenSource
Agile
Continuous Delivery
Craftsmanship
DÉVELOPPEMENT
Fast Data
Smart Data
Big Data
Data Science
DATA
Chaînes Devops
Infrastructure as Code
Cloud
Hosting / Infogérance
DEVOPS & CLOUD

Ippon Technologies © 2017
Recrutement sur Lyon

#Me
Steve HOUËL
Solution Architect
shouel@ippon.fr
JHipster contributor
JHipster Lyon Meetup manager
https://www.meetup.com/fr-FR/JHipster-Lyon/
Certified AWS Solution Architect
https://blog.ippon.fr/2017/06/09/les-architectures-serverless/
@SteveHouel stevehouel
www.ippon.fr
blog.ippon.fr

Back to the past

What is Serverless
Well… It means no servers right ?
● No need to manage servers
● No need to even think about servers
● No need to provision infrastructure
● Pay only for what to use
● Use backend as a Service (BaaS)
● Deploy function not apps (FaaS)
● It’s event based/oriented
● Initially designed for Mobile application

What isn’t serverless ?
adrian cockcroft @adrianco
If your PaaS can efficiently start instances in 20ms that
run for half a second, then call it serverless.
PaaS
Container
#NoOps

Who does serverless

But… what does that really mean ?
Virtual machine

But… what does that really mean ?
Virtual machine Virtual machine

But there is a problem
Over provisioned
= Cost money

Let’s try another way
Virtual machine

Over provisioned
= Cost money

Another again ? Shrink the unit of compute

Separate function scale independently
Function 1
Function 2
Function 3
- Scale independently
- Isolate
- Stateless / ephemeral
- Match your traffic pattern

Cloud services
emit “events”
Functions can write
back to the cloud
External services
emit “events”
Overview
{...}
Or call other APIs
2
1
3
4

Use case : Serverless Webapp

Use case : File processing

handler.js (lambda AWS)
'use strict';
module.exports.hello = (event, context, callback) => {
const response = {
statusCode: 200,
body: JSON.stringify({
message: 'Go Serverless v1.0! Your function executed successfully!',
input: event,
}),
};
callback(null, response);
};

Benefits
● Reduced operational cost
● BaaS - reduced development cost
● FaaS - scaling cost
● Optimization is the root of some cost
savings
● ‘Greener’ computing

Drawbacks
● Vendor lock-in
● Security concerns
● Loss of Server optimizations
● Implementation drawbacks:
● Execution duration
● Startup latency
● Tests
● Deployment / packaging / versioning

Develop Serverless : Serverless Framework
● serverless.com
● Announced at re:Invent 2015 by Austen Collins and Ryan Pendergast
● Supports NodeJS, Java, Python, ...
● Can be deployed on AWS, Google Cloud Platform, IBM OpenWhisk,
Microsoft Azure
● Manage your infrastructure (bucket, API Gateway, …)
● Simple configuration in YAML

Serverless “Hello World” API
$ serverless create --template aws-nodejs
Edit handler.js, serverless.yml
$ serverless deploy [--stage stage_name]
$ serverless invoke [local] --function function_name
$ serverless info
$ curl $URL
$ serverless remove

Develop Serverless : Chalice
● Released in July 2016, currently on 1.0.2
● Simply add your Python code
➔deploy with a single call and zero config
➔API and IAM policy are created automatically and auto-generated
● Run locally your API on port 8000 (Flask)
● Fast & lightweight framework
● Oriented API Call not infrastructure

Chalice “HelloWorld” API
$ chalice new-project s3test && cd s3test
Write your function in app.py
$ chalice local
● $ http put http://localhost:8000/objects/document.json value1=123
● $ http get http://localhost:8000/objects/document.json
$ chalice deploy
$ chalice url

Conclusion

PARIS
BORDEAUX
NANTES
LYON
MARRAKECH
WASHINGTON DC
NEW-YORK
RICHMOND
MELBOURNE
rdespinasse@ippon.fr
www.ippon.fr - www.ippon-hosting.com - www.ippon-digital.fr
@ippontech
-
06 66 93 60 05

To be or not to be Serverless

Recommended

Recommended

More Related Content

What's hot

What's hot (19)

Similar to To be or not to be Serverless

Similar to To be or not to be Serverless (20)

Recently uploaded

Recently uploaded (20)

To be or not to be Serverless

Editor's Notes