AWS User group Hannover - Serverless - a field report

A talk from the AWS user group Hannover, Germany. A short overview of why serverless is a great way to go, especially while building new applications.

Transcript

1. Serverless A field report Nico Schilling 09.01.2018
2. From the old world to the new one…
3. The (r)evolution in infrastructure From the old world to the new one…
4. The problems with the castles… Organizational wise • Too many players involved • Too many processes involved Technical wise • Very complex software • Deployments are risky • No continuous deployment • There is not a single person who can understand the app in a whole • Difficult to scale From the old world to the new one… www.flickr.com/photos/shanerielly/4163903111/in/photostream/lightbox/
5. Why are Containers not the general solution? Containers help developers to stop building monolithic applications One Container = One Process But most parts remain in the hand of the classic IT department • Secure Networks (Firewall, IP ranges …) • Secure hosts (Patching, audit processes) • Resource handling (CPU, RAM, Storage) • Access Control From the old world to the new one…
6. Where can serverless help? • Helps concentrate on business processes and their data • Helps to push the idea of microservices • It scales nearly endless • Highly available and secure • No upfront costs, pay for your demand • No patching, less network From the old world to the new one…
7. Responsibilities From the old world to the new one… Physical + Private Cloud IaaS + Containers PaaS + Serverless Application / Software Data Application Server, DB, ... OS Virtualization Hardware Networking Datacenter Facilities
8. We need infrastructure we do not have to care about! It just has to work for us!
9. The goal: You build it, you run it!
10. Shift of responsibilities From the old world to the new one… DAVE - Developer ABIGAIL - Administrator
11. Serverless AWS Services
12. What does AWS provide? Serverless AWS Services … and many more!
13. Serverless for everything?
14. Limits of serverless There are some limits. Among others: • For event-driven use cases • Processing time and resources are limited • Local testing is limited • Latency / reaction time / cold starts • Very limited control over the base environment • Cold starts Serverless for everything?
15. Cold starts Serverless for everything? https://read.acloud.guru/does-coding-language-memory-or-package-size-affect-cold-starts-of-aws-lambda-a15e26d12c76
16. Vendor lock-in There is a kind of vendor lock-in… By why is this not so important? • Base offerings are equal between the providers • Abstraction in the software can help • Use a language which is known and available on all platforms • There always was a kind of lock-in Serverless for everything? Designed by Rawpixel.com
17. Which services are not serverless and why? There are a couple of services which seem to be serverless, but they are not. They are managed by AWS, but some features are missing: • Scalability • Availability Serverless for everything?
18. Let‘s talk about use cases
19. Operations view For running an application we need an environment: • CI / CD (Code*) • Canary Deployment / Traffic shifting • Event Monitoring. (Cloudwatch) • Log consolidation / analytics (Cloudwatch) • Detailed runtime analysis (X-Ray) Let‘s talk about use cases
20. How monolithic architectures look like? Let‘s talk about use cases Database Application Presentation
21. Where can serverless be used? Let‘s talk about use cases Automation Business software
22. Cloud-native architectures are small pieces, loosely joined
23. Extension for AWS CloudWatch Let‘s talk about use cases AWS Cloud Region Administrator CloudWatch time event Email notification Webserver https://github.com/n-schilling/awssslchecker
24. AWS Cloud Region Emailsystem Email Compliance email archive Let‘s talk about use cases Auditor Data flow Used indirectly https://github.com/n-schilling/ceca
25. You need a GUI? Let‘s talk about use cases AWS Cloud Region Auditor Client Vue.js
26. Handle Whitepaper Downloads? Let‘s talk about use cases AWS Cloud Region User E-Mail with signed S3 url
27. THANK YOU! Let’s stay in touch LinkedIn: www.linkedin.com/in/nicoschilling/ Email: nico.schilling@nordcloud.com