This document summarizes a presentation about serverless computing and open source functions. It discusses how serverless platforms abstract away servers to allow developers to focus on code without worrying about infrastructure. It also describes Fn, an open source functions platform, and how functions are packaged as containers that can be deployed on Fn. Finally, it discusses principles for driving business value, increasing efficiency, and improving team happiness with serverless.
Your FaaS platform will enable your app to scale organically per-request without you having to write any special code to handle it. And not just the gentle seasonal changes in demand that a retail business might experience but also sudden, dramatic surges in demand caused by your app going viral.
Fn is an open source Function-as-a-Service platform. It was announced by Oracle today/this week. You can download this now and use it for real.
It’s an Apache 2.0 licensed project.
We are actively seeking outside collaborators.
We have teams in the US and UK committed to working in the open on this project.
Not ‘open core’. We are not keeping anything back for ourselves – what you see in the github is what we’ll be running in our cloud service.
Why? - Being open allows us to provide a much better developer esperience.
Not only can you get and read the source so you know exactly what’s going on under the hood (should you need to)…
…but you can contribute to shape the project to better meet your needs.
But mainly because it enables an awesome, frictionless local developer experience that is difficult or impossible with closed, propietary solutions.
You may hear the phrase “functainer”.
I hope we’re past this point.
Cloud isn’t a datacenter in the sky.
Abstractions are a good thing
Jevons Paradox: late 1800’s, William Jevon: technological improvements that increased the efficiency of coal-use led to the increased consumption of coal in a wide range of industries
There’s some merit to the expression No Ops, but no, it doesn’t exist.
In fact it’s now more important than ever
We don’t have our friends running ops down the hall who we can work with whenever something goes wrong
It’s early
Ecosystem is growing
Tooling is evolving
Frameworks to make it easier
Ensure proper ci/ci
Best praciteices provided by paved road.
Everything is a service: focus on services not servers
DevOps have to understand the constraints of services (e.g. db performance)
Parse would shut customers down who were doing table scanning to maintain good overall performance.
Less Code: more complexity pushed down so less code for devs, but just moved the problem. More elegant code
So you must design for them, and degrade the quality of your application gracefully to minimize the impact on your users.
Cold starts can heavily influenced by both language runtime and memory allocation. A cold start in an intermediate service can easily cause the outer service to timeout.
Specialsts running each service that your function uses—let’s team focus on problem they are working on and not
Owners of all codde event if using service managed by others.
DevOps can also use serverless, scaning jbos, auditing,
Single slide describing Oracle Functions (good to give this to others to incorporate in their decks)