e637f9736e
now we can run multiple lbs in the same 'cluster' and they will all point to the same nodes. all lb nodes are not guaranteed to have the same set of functions nodes to route to at any point in time since each lb node will perform its own health checks independently, but they will all be backed by the same list from the db to health check at least. in cases where there will be more than a few lbs we can rethink this strategy, we mostly need to back the lbs with a db so that they persist nodes and remain fault tolerant in that sense. the strategy of independent health checks is useful to reduce thrashing the db during network partitions between lb and fn pairs. it would be nice to have gossip health checking to reduce network traffic, but this works too, and we'll need to seed any gossip protocol with a list from a db anyway. db_url is the same format as what functions takes. i don't have env vars set up for fnlb right now (low hanging fruit), the flag is `-db`, it defaults to in memory sqlite3 so nodes will be forgotten between reboots. used the sqlx stuff, decided not to put the lb stuff in the datastore stuff as this was easy enough to just add here to get the sugar, and avoid bloating the datastore interface. the tables won't collide, so can just use same pg/mysql as what the fn servers are running in prod even, db load is low from lb (1 call every 1s per lb). i need to add some tests, touch testing worked as expected.
Oracle Functions 
Oracle Functions is an event-driven, open source, functions-as-a-service compute platform that you can run anywhere. Some of it's key features:
- Write once
- Run anywhere
- Public, private and hybrid cloud
- Import functions directly from Lambda and run them wherever you want
- Easy to use for developers
- Easy to manage for operators
- Written in Go
- Simple yet powerful extensibility
Prequisites
- Docker 17.05 or later installed and running
- Logged into Docker Hub (
docker login)
Usage
Installation (if running locally)
NOTE: The following instructions apply while the project is a private repo. This will build the Functions server and the CLI tool directly from the repo instead of using pre-built containers. Once the project is public, these steps will be unnecessary.
# Build and Install CLI tool
cd fn
make dep # just once
make install
# Build and Run Functions Server
cd ..
make dep # just once
make run # will build as well
Installation (if using internal alpha service)
Set your system to point to the internal service on BMC:
export API_URL=http://129.146.10.253:80
Download the pre-built CLI binary:
- Visit: https://gitlab-odx.oracle.com/odx/functions/tree/master/fn/releases/download/0.3.2
- Download the CLI for your platform
- Put in /usr/local/bin
- chmod +x
Your First Function
Functions are small but powerful blocks of code that generally do one simple thing. Forget about monoliths when using functions, just focus on the task that you want the function to perform.
The following is a simple Go program that outputs a string to STDOUT. Copy and paste the code below into a file called func.go. Currently the function must be named func.your_language_extention (ie func.go, func.js, etc.)
package main
import (
"fmt"
)
func main() {
fmt.Println("Hello from Oracle Functions!")
}
Now run the following CLI commands:
# Initialize your function
# This detects your runtime from the code above and creates a func.yaml
fn init <DOCKERHUB_USERNAME>/hello
# Test your function
# This will run inside a container exactly how it will on the server
fn run
# Deploy your functions to the Oracle Functions server (default localhost:8080)
# This will create a route to your function as well
fn deploy myapp
Now you can call your function:
curl http://localhost:8080/r/myapp/hello
Or in a browser: http://localhost:8080/r/myapp/hello
That's it! You just deployed your first function and called it. Now to update your function
you can update your code and run fn deploy myapp again.
To Learn More
- Visit our Functions Tutorial Series
- See our full documentation
- View all of our examples
- You can also write your functions in AWS Lambda format
Get Involved
- TODO: Slack or Discord community
- Learn how to contribute
- See milestones for detailed issues
User Interface
This is the graphical user interface for Oracle Functions. It is currently not buildable.
docker run --rm -it --link functions:api -p 4000:4000 -e "API_URL=http://api:8080" treeder/functions-ui
For more information, see: https://github.com/treeder/functions-ui
Next up
Check out the Tutorial Series.
It will demonstrate some of Oracle Functions capabilities through a series of exmaples. We'll try to show examples in most major languages. This is a great place to start!