a32ca3d90a
* moving documentation around to be more clear and easier to browse - moved assets into their own directory and updated links to them - moved operating docs into their own directory - consolidated kubernetes docs - added docker-swarm folder for docs - updated docs layout in docs/README.md to reflect the changes and make it easier to read * docs: s/Operating Functions/Operating IronFunctions/ * docs: removing duplicate database link * docs: moving databases into general docs * docs: moving databases/mqs back * docs: removing memory.md (duplicate of operating/routes.md) * docs: converting to markdown bullets
1.3 KiB
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.