Uploaded byEran Stiller
It's a Serverless World
The document provides an overview of serverless computing including definitions of functions-as-a-service (FaaS), containers-as-a-service (CaaS), and serverless application platforms. It discusses benefits, challenges, and practical applications of serverless technology, emphasizing its efficiency in system integration and the necessity for meticulous planning and automation. Additionally, it highlights the potential for on-premise serverless solutions, primarily targeting developers and organizations looking to leverage cloud-native architectures.
More Related Content
Similar to It's a Serverless World
![[Capitole du Libre] #serverless - mettez-le en oeuvre dans votre entreprise...](https://cdn.slidesharecdn.com/ss_thumbnails/capitoledulibre2018serverless-181120135943-thumbnail.jpg?width=640&height=640&fit=bounds)
It's a Serverless World
- 2. It’s a ServerlessWorld Eran Stiller Chief Technology Officer erans@codevalue.net @eranstiller https://stiller.blog https://codevalue.net
- 3.
- 4. Agenda ▪ Serverless 101 ▪Functions-as-a-Service (FaaS) ▪ Containers-as-a-Service (CaaS) ▪ Serverless Application Platform ▪ On-Premise Serverless 4
- 5. About Eran Eran Stiller ▪@eranstiller ▪ CTO & Founder at CodeValue ▪ Software architect, consultant and instructor ▪ Microsoft Regional Director & Azure MVP ▪ Founder of Azure Israel Meetup 5
- 6.
- 7. Serverless is anAbstraction 8 Serverless Containers Cloud Virtualization Bare-Metal
- 8. Focus on YourCore Business 9
- 9. It’s the Economy,Stupid! 10
- 10. It’s Not AllPositive ▪ Slow cold start ▪ Monitoring ▪ Debugging ▪ Governance 11
- 11. Serverless Isn’t New ▪S3/Blob Storage ▪ Message Queues-as-a-Service ▪ Database-as-a-Service ▪ Identity-as-a-Service ▪ Serverless Compute is relatively new 12
- 12. Serverless Compute ▪ Functions-as-a-Service(FaaS) ▪ Containers-as-a-Service (CaaS) ▪ Serverless Application Platform 13
- 13.
- 14. Functions-as-a-Service (FaaS) ▪ Deployindividual “functions” ▪ Triggered by various sources ▪ Theoretically, each function is individually managed and deployed ▪ Expected to start within milliseconds ▪ Process individual requests and exit ▪ Scales according to load ▪ Oblivious to infrastructure used to execute code 15
- 15.
- 16.
- 17. FaaS Scenarios ▪ Systemintegration ▪ Glue ▪ Scheduled tasks ▪ Dynamic Workloads ▪ Huge volume 18
- 18. A Function asa Nano-Service ▪ A Function is just a really, really small micro microservice ▪ Best practices for microservices still apply 19
- 19. General Practices forFaaS ▪ Thick clients; thin & stateless back-ends ▪ Sync is nice, but Async is nicer ▪ Live and die by the cloud
- 20. Suggestions for GettingStarted ▪ For existing services, start small ▪ Replace 1 API or background processing item ▪ Integration is a great place to introduce Serverless ▪ It is often a new layer on top of old layers ▪ For new services, establish a pattern early and stick with it ▪ Lack of tooling/established patterns mean you pay an early adopter tax ▪ Build automation ASAP
- 21. Containers as aService (CaaS) 22
- 22. Containers-as-a-Service (CaaS) ▪ Traditionally,containers are scheduled to run on VMs ▪ Either manually or by an orchestrator ▪ You manage the VMs and scale them ▪ Native cloud vendor solutions manage and scale the VMs for you ▪ But this is still at the VM level ▪ Using CaaS you forget about VMs ▪ Schedule a container when required ▪ Pay for resources (CPU & RAM) per use 23
- 23.
- 24.
- 25. Serverless Containers Scenarios ▪Scheduled tasks ▪ Dynamic Workloads ▪ Huge volume 27
- 26.
- 27.
- 28. Service Fabric Mesh ▪A serverless application platform ▪ Allows developers to deploy containerized workloads ▪ Only pay for what you are using ▪ Provides multiple capabilities out-of-the-box ▪ No Infrastructure ▪ Containers ▪ Intelligent Traffic Routing ▪ Built-in support for Envoy ▪ Scalability ▪ Easy Deployments 30
- 29. A New ApplicationModel ▪ Application ▪ Networks ▪ Secrets ▪ Volumes ▪ Routing Rules ▪ Auto-Scaling Rules 31
- 30.
- 31.
- 32.
- 33. On-Premise Serverless Compute ▪Most Serverless Compute offerings are in the public cloud ▪ Some solutions are available for On-Premise deployment as-well ▪ E.g. Azure Functions ▪ Completely open source ▪ Can be run in a custom Docker Container ▪ Used in Azure IoT Edge, Azure IoT DataBox, etc. 35
- 34. On-Premise FaaS ▪ KubernetesBased Platforms ▪ Fission ▪ Kubeless ▪ Funktion ▪ OpenWhisk ▪ Apache incubator project ▪ All of these are an abstraction on top of Docker 36
- 35. Fission ▪ Framework forServerless functions on Kubernetes ▪ Support multiple environments ▪ Node.js ▪ Python ▪ PHP ▪ Ruby ▪ Go ▪ .NET Core 37
- 36.
- 37.
- 38. Takeaways ▪ Serverless computeis an evolution of PaaS ▪ An abstraction on top of containers ▪ Mainly in the cloud but also on-premise ▪ Very efficient for system integration ▪ “Glue” scenarios ▪ Can create an entire system on Serverless ▪ Requires meticulous planning and execution ▪ Automation is key! 40
- 39. Is Serverless forMe? ▪ It depends ▪ Current culture ▪ The distance to “Cloud Native” ▪ A new architecture ▪ Requires thinking differently ▪ Requires mature and robust CI/CD and automation systems ▪ DevOps doesn’t just become ‘NoOps’ 41
- 40.
- 41. Eran Stiller Chief TechnologyOfficer erans@codevalue.net @eranstiller https://stiller.blog https://codevalue.net