alihan/fn-serverless
1
0
Fork 0
mirror of https://github.com/fnproject/fn.git synced 2022-10-28 21:29:17 +03:00
Code Issues Packages Projects Releases Wiki Activity
Files
41c06644d97ab38e1f1c2c3f60a041c4e43f397c
fn-serverless/docs/mqs
History
Travis Reeder 41c06644d9 Docs related to running in production. (#174) 
* Fixed up api.md, removed Titan references.

* Adding more documentation on running in production.

* Update deps for ironmq.
2016-10-17 11:31:58 -07:00
..
README.md
Docs related to running in production. (#174)
2016-10-17 11:31:58 -07:00

README.md

Message Queues

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

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

docker run -e "MQ=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 IronFunctions 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.