Skip to content

Why Okra

Fernando Nogueira edited this page May 19, 2017 · 1 revision

Why or when should I use Okra?

There a plenty of messaging brokers available out there. That's right...

But there are some challenges when we talk about task scheduling and we try to find out a simple, yet scalable, solution to solve these challenges.

What tool or message broker do you use when you need to:

  • Schedule actions that need to get fired after a long time (days, maybe) ?
  • What about when these actions take a long time to finish executing?
  • Schedule recurrent actions? Like "do this action every 30 minutes"
  • Guarantee that the scheduled action will not get lost even when your application dies?
  • Guarantee that your scheduled action will be executed only once, even if you have a lot of workers processing different actions across multiple servers?

That's why you should use Okra if you have these needs!

I needed this kind of task scheduling some times during my career and I did not succeeded finding a tool or message broker that solved all these items.

Feel free to use, contribute and share Okra! ;)

Clone this wiki locally