Files
fn-serverless/docs/operating/mqs
Travis Reeder 9cc12b4b12 Remove iron...
2017-05-18 18:59:34 +00:00
..
2017-05-18 18:59:34 +00:00

Message Queues

A message queue is used to coordinate asynchronous function calls that run through Oracle Functions.

We currently support the following message queues and they are passed in via the MQ_URL environment variable. For example:

docker run -e "MQ_URL=redis://localhost:6379/" ...

Bolt (default)

URL: bolt:///titan/data/functions-mq.db

See Bolt in databases above. The Bolt database is locked at the file level, so the file cannot be the same as the one used for the Bolt Datastore.

Redis

See Redis in databases above.

IronMQ

URL: ironmq://project_id:token@mq-aws-us-east-1.iron.io/queue_prefix

IronMQ is a hosted message queue service provided by Iron.io. If you're using Oracle Functions in production and don't want to manage a message queue, you should start here.

The IronMQ connector uses HTTPS by default. To use HTTP set the scheme to ironmq+http. You can also use a custom port. An example URL is: ironmq+http://project_id:token@localhost:8090/queue_prefix.

What about message queue X?

We're happy to add more and we love pull requests, so feel free to add one! Copy one of the implementations above as a starting point.