Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Differences from an AMQP server #17

Closed
DanielVartanov opened this issue Oct 24, 2017 · 4 comments
Closed

Differences from an AMQP server #17

DanielVartanov opened this issue Oct 24, 2017 · 4 comments

Comments

@DanielVartanov
Copy link

DanielVartanov commented Oct 24, 2017

Faktory looks like a decent message broker. But how do I advocate it to my teammates over, say, RabbitMQ?

@mperham
Copy link
Collaborator

mperham commented Oct 24, 2017

Faktory is not really a message queue and RabbitMQ is not really a background job system. If you want to send arbitrary messages between different apps written in different languages in your business, that's more Rabbit's strength. Faktory imposes certain conventions like retries, job arguments, etc that are more specialized than just general message passing. OTOH, that lets the Faktory Web UI show you much more interesting data about each element.

Faktory's strength is that it is much easier to setup. Rabbit can be complex.

@Skeyelab
Copy link

"Faktory's strength is that it is much easier to setup. Rabbit can be complex."

So far you do not support OSX nor Heroku. It is not very easy to set up.

@mperham
Copy link
Collaborator

mperham commented Oct 25, 2017

@Skeyelab you're comparing a 1 day old project with a 15 yr old project. give it time.

@mperham mperham closed this as completed Oct 25, 2017
@Skeyelab
Copy link

Fair.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants