Fn meetup by Sardar Jamal Arif
0 likes•208 views
The document outlines Oracle's serverless computing offerings, detailing the evolution from baremetal servers to virtual machines, containers, and today’s serverless architecture. It emphasizes the benefits of using functions as a service, which allow for increased productivity and cost efficiency by eliminating infrastructure management responsibilities. The fn project is introduced as an open-source platform that supports functions packaged as containers and integrates smoothly with various environments.
Fn meetup by Sardar Jamal Arif
- 1. Jamal Arif Oracle Cloud Infrastructure Serverless 1 sort of ..
- 2. Safe harbor statement The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, timing, and pricing of any features or functionality described for Oracle’s products may change and remains at the sole discretion of Oracle Corporation. 2
- 3. Super quick history lesson… 3
- 4. Baremetal servers …. Dedicated Physical Server Deployment ~ months Hardware Kernel / OS Dependencies Application Ship and install hardware Install Operating System Install software needed to serve application Install application code
- 5. Way too many problems …. • Monolithic Apps • Slow deployment times • Huge Costs • Wasted Resources • Difficult to Scale • Difficult to migrate • Vendor Lock in
- 6. Hypervisor based virtualization.. Ship and install hardware Install Operating System in a VM Install software needed to serve application Install application code Hypervisor based Virtualization Deployment ~ days (mins) Hardware + Hypervisor Kernel / OS Dependencies Application VM Kernel / OS Dependencies Application VM
- 7. Better but still limited…. • Each VM still requires CPU allocation, storage, RAM, An entire Guest OS • Guest OS à Wasted resources • Application tied to the OS, multiple instances of application need multiple VMs • More VMs à More resources
- 8. Hypervisor based virtualization.. Ship and install hardware Install Operating System in a VM Build container with app software add application code to container Containers Deployment ~ mins (secs) Hardware Kernel/OS Dependencies Application Container Dependencies Application Container
- 9. Containers are everywhere... • Portable and efficient • No dependencies on the kernel or the Hardware • Can run on baremetal or VMs • Applications packaged in a container speeds deployment (CI/CD) • Provides a path for micro-services application architecture
- 10. Serverless… Ship and install hardware Install Operating System in a VM Build container with app software Write application code Functions Unit of deployment - Functions (micro-seconds)
- 11. Serverless .. (sort off..) • You don’t have to “think” about infrastructure • You are not responsible for: • Turning infrastructure on/off • Scaling infrastructure up/down • Monitoring infrastructure • As a result: • You are more productive (faster feedback loop) • You only pay for actual usage, not for idle time • Unit of deployment is a Function ..
- 12. Evolution of Compute …. Virtual machines FunctionsContainersBare Metal
- 13. A serverless platform key properties.. • Open Source - no vendor lock-in • Platform Independent - laptop, server, cloud • Approachable - easy for new users, low level controls for advanced users • Container/Docker Based - leverage Docker ecosystem • Scheduler/orchestrator Independent - deploy to Kubernetes, Swarm, Mesos, etc.
- 15. Introducing the Fn Project ● Open-source Functions platform ● Can be deployed to any cloud and on-premise ● Simple, elegant, and extensible by design ● Containers are primitives ● Active 3200+ commits across 60+ contributors ● Independently governed with representation at Container Native Compute Foundation (CNCF) ● Strong enterprise focus (security, scalability, observability, etc.) 15
- 16. Functions == Containers Functions are packaged as containers—so any container can be deployed as a function Package and reuse open source libraries as functions!
- 18. Oracle Functions Autonomous Platform auto-scales functions No servers to provision, manage Pay Per Use Pay for execution, not for idle time No Lock-in Built on open-source Fn Project and Docker Functions-as-a-Service Oracle Cloud Integrated Container Native Multi-tenant Secure Open Source Engine
- 19. Functions Overview Push container to registry Configure function trigger Code runs only when triggered Pay for code execution time only Identity OCI Services Registry Network Logging Monitoring OCI Events Direct Invoke (SDK/CLI/API) Function Triggers Function Integrations 19
- 21. Function Development Kits (FDKs) Simply write a `handler` function that adheres to the FDK’s interface and the FDK will provide the input to your function, as well as deal with returning the proper output format. FDKs make it easy to write functions 21
- 22. Use Cases – “Run Code in Response to Events” Web, Mobile, IoT Backends Real-time File, Stream Processing DevOps, Batch Processing Glue Cloud Services, Event- driven
- 23. Demo