Dave Syer 9321dc7311 Remove function composition from the catalog interface
Should be easy enoug hto add back later, but it was causing issues
with type conversion where we are npot yet sophisticated enough
to chain functions together and keep track of the types being
passed between them.
2017-01-10 12:37:29 -05:00
2017-01-03 08:18:31 -05:00
2016-09-21 22:33:06 -04:00
2017-01-03 08:18:31 -05:00
2017-01-03 08:18:31 -05:00

== Register a Function:

----
./registerFunction.sh -n uppercase -f "f->f.map(s->s.toString().toUpperCase())"
----

== Run a Stream Processing Microservice using that Function:

----
./stream.sh -i words -o uppercaseWords -f uppercase
----

== Run a REST Microservice using that Function:

----
./web.sh 
curl -H "Content-Type=text/plain" localhost:8080/uppercase -d foo
----

== Compose Functions:

(assuming the `uppercase` function was already registered as above)

----
./registerFunction.sh -n pluralize -f "f->f.map(s->s+\"S\")"

curl -H "Content-Type=text/plain" localhost:8080/uppercase,pluralize -d foo
----

== Run a Task Microservice using a Supplier, Function, and Consumer:

(assuming the `uppercase` function was already registered as above)

----
./registerSupplier.sh -n words -f "()->Flux.just(\"foo\",\"bar\")"

./registerConsumer.sh -n print -f "System.out::println"

./task.sh -s words -f uppercase -c print
----

(more docs soon)
Description
No description provided
Readme Apache-2.0 16 MiB
Languages
Java 99.5%
Shell 0.4%