Serverless architecture is a hot topic nowadays. The traditional architecture needs to have one or many servers to let the app run on, make the app come out the market. Many steps have been done from managing servers, monitoring servers to optimizing servers and it needs server administration knowledge. With Serverless, it doesn't mean you don't need the server at all, it means the server will be hosted by another party and away from you. You only focus on your code and give your product out to the market as fast as possible.

1. München/HQ Bamberg Berlin Đà Nẵng Dresden Grenoble Hamburg Cologne Leipzig Nuremberg Prague Washington Zug
Serverless architecture
Trung Huynh

2. 16.04.17 2
§ Software engineer at mgm technology partners Vietnam
§ Java
§ JavaScript
§ Server administrator
§ Trung.Huynh@mgm-tp.com
Huynh Thanh Trung

3. 16.04.17 3
mgm technology partners
We build software
§ Web & mobile
§ Large enterprise customers in Germany
We use state of the art technologies
§ J2EE, Spring, Hibernate
§ Angular, REACT
§ Postgres, Oracle

4. 16.04.17 4
We are proud of our Engineers
500+ Engineers world wide
eGovernment Insurance eCommerce

5. 16.04.17 5
We are proud of our Engineers in Vietnam
38 Engineers in Da Nang
Operating since January 2016

6. 16.04.17 6
§ Who has heard of / read about Serverless-architecture?
§ Who has used / written with Serverless in mind?
Warming questions

7. 16.04.17 7
Agenda
1. What is Serverless?
2. Backend as a Service
3. Function as a Service
4. Benefits and Drawbacks
5. Sample
6. Q & A

8. 16.04.17 8
Who is using Serverless?

9. 16.04.17 9
Typical server characteristics
Access control
Load and
performance
Right-sizing
Auto-scaling
Configuration

10. 16.04.17 10
§ You still need servers. You don’t manage them anymore
§ You need:
§ 3rd party services
§ Client-side logic
§ Functions as a Service
What is Serverless?

11. 16.04.17 11
Traditional vs Serverless architecture

12. 16.04.17 12
Evolution of cloud-hosted

13. 16.04.17 13
Agenda
3. Function as a Service
4. Benefits and Drawbacks
5. Sample
6. Q & A
2. Backend as a Service
1. What is a Serverless?

14. 16.04.17 14
§ Services provided via the API
§ Our data will be hosted and processed by the 3rd party
Backend as a Service

15. 16.04.17 15
Dynamo DB

16. 16.04.17 16
Agenda
2. Backend as a Service
4. Benefits and Drawbacks
5. Sample
6. Q & A
3. Function as a Service
1. What is a Serverless?

17. 16.04.17 17
§ Independent server-side logic functions
§ Scalable
§ Fully managed by 3rd party
§ Event-triggered
Functions as a Service

18. 16.04.17 18
Event Source

19. 16.04.17 19
Lambda function sample
Multiply numbers

20. 16.04.17 20
Agenda
2. Backend as a Service
3. Function as a Service
5. Sample
6. Q & A
4. Benefits and Drawbacks
1. What is a Serverless?

21. 16.04.17 21
Benefits

22. 16.04.17 22
Never pay for idle

23. 16.04.17 23
AWS EC2 AWS Lambda
• Instance: t2.small, 1 CPU and 2 GB RAM • 10 functions with 1 million calls / month
• Memory: 256 Mb
• Execution time: 500 ms per call
Pricing comparison
Pricing formula: {number of function}
x {number of call} x
{memory} * {exec-time} / 1024
22$ / month

24. 16.04.17 24
Drawbacks
Loss Server optimization Vendor lock-in Client-side logic repetition

25. 16.04.17 25
Agenda
2. Backend as a Service
3. Function as a Service
4. Benefits and Drawbacks
6. Q & A
5. Sample
1. What is a Serverless?

26. 16.04.17 26
Requirement

27. 16.04.17 27
Architecture diagram

28. 16.04.17 28
Agenda
2. Backend as a Service
3. Function as a Service
4. Benefits and Drawbacks
5. Sample
6. Q & A
1. What is a Serverless?

29. 16.04.17 29
Innovation Implemented.
mgm technology partners GmbH
Frankfurter Ring 105a
80807 München
Tel.: +49 (89) 35 86 80-0
Fax: +49 (89) 35 86 80-288
http://www.mgm-tp.com
PragMunich Berlin Hamburg Cologne NurembergGrenoble LeipzigDresdenBamberg Đà Nẵng ZugWashington