Welcome to the Function Service Overview Module. What is Oracle Functions? Oracle Functions is a serverless functions as a service offering. It is fully integrated with the Oracle Cloud infrastructure. Functions is a container native platform, which means your functions are deployed as Docker images and run as Docker containers. Functions is based on the open source FN project. Functions are secured using Oracle Cloud security constructs such as networking, identity and access management compartments, and many more. Let's look at some of the benefits of Oracle Functions. Functions is a paper use platform, which means you only pay for the function execution and you're not paying anything if your functions are idle. The platform is autonomous, so it takes care of provisioning, managing, and auto-scaling your functions for you and as a user, you do not have to worry about any of these concerns. It's an event-driven platform, there are a number of Oracle Cloud infrastructure services which can automatically trigger your function code for you. How does it work? May give you a function CLI. You write your function code, and you run a command that will package the function called as a Docker image and push this function image to a registry. The next step, you will configure a function trigger. Now what is the function trigger? A function trigger is the condition when you want to execute this function. An example of a function trigger is an HTTP request made to invoke the function. Your code will run only when it is triggered. In this example, your code will run when somebody makes a request to invoke your function, and you pay only for the code execution time, so there is no charge for idle time. Let's look at the function pricing. There are two dimensions, one is the number function invocation requests, and the second one is the resource usage, which is the amount of memory that you consume when your function was running. Functions pricing has an imbedded generous free tier to the first two million requests and 400,000 gigabytes seconds per month. About that, when you exceed the free tier, there is a small charge that you pay for using additional requests and additional gigabyte seconds. R3 requests are twice the number of AWS Lambda three requests and our DB second pricing is 15 person less than AWS Lambda. Functions is Polyglot and container native. Functions are packaged as Docker images and run as containers. This led to package and reuse open source libraries as functions. We have ridged support and function development kits or FDKs, or Python, Java, Go, Node, and Ruby. For advanced use cases, we allow you to bring your own and customize the FN generated Docker file. We allow you to use Micronaut, Microservices framework, and Graal VM native, which will help you reduce your Docker image size and memory footprint. Let's move to functions integrations. There are a number of services in OCI that can trigger functions automatically for you. Like the event service, the API Gateway, and so on. We can also use the CLI and the SDK to trigger your functions. When your function is triggered, we pull the Docker image from the OCI registry and start the function containers. In your function code, you can use any of your downstream services like object storage, autonomous, compute the Secret Service, Net-booking and many other services. Any logs, metrics, and traces that are generated are sent to CI logging, monitoring, and APM services respectively.
