ruote final

An old private deck from 2011, made public in 2017

Transcript

1. ruote
2. which storage? managing while in prod ruote-fluo
3. which storage? managing while in prod ruote-fluo
4. Storage storages ‣ Ruote::HashStorage ‣ Ruote::FsStorage ‣ Ruote::Dm::Storage ‣ Ruote::Sequel::Storage ‣ Ruote::Redis::Storage ‣ Ruote::Mon::Storage ‣ Ruote::Couch::Storage
5. ‣ multiple workers ? ‣ worker on same host as db ? Storage
6. Storage http://ruote.rubyforge.org/configuration.html#storage
7. ‣ what db will your application use ? ‣ what db is your administrator comfortable with ? Storage
8. storages ‣ Ruote::HashStorage ‣ Ruote::FsStorage ‣ Ruote::Dm::Storage ‣ Ruote::Sequel::Storage ‣ Ruote::Redis::Storage ‣ Ruote::Mon::Storage ‣ Ruote::Couch::Storage Storage
9. multiple workers?
10. because ‣ of the GIL ‣ workers crash Storage
11. A Global Interpreter Lock (GIL) is a mutual exclusion lock held by a programming language interpreter thread to avoid sharing code that is not thread-safe with other threads. In languages with a GIL, there is always one GIL for each interpreter process. CPython and CRuby use GILs. Applications written in programming languages with a GIL can be designed to use separate processes to achieve full concurrency, as each process has its own interpreter and in turn has its own GIL. Otherwise, the GIL can be a significant barrier to concurrency—a price paid for having the dynamism of the language. http://en.wikipedia.org/wiki/Global_Interpreter_Lock
12. webserver
13. webserver
14. webserver main thread request thread request thread request thread ruby process
15. webserver main thread request thread request thread request thread ruote worker main thread dispatch thread dispatch thread ruby process
16. evading the GIL ‣ event loop (event machine) ‣ patched rubies (ree) ‣ jruby, rubinius (no gil) ‣ multiple ruby processes
17. evading the GIL ‣ event loop (event machine) ‣ patched rubies (ree) ‣ jruby, rubinius (no gil) ‣ multiple ruby processes ‣ more memory, more power
18. ruote worker ruby process webserver
19. ruote worker webserver ruby processes
20. ruby processes ruby processes ruote worker ruote dashboard webserver
21. ruby processes ruby processes ruote worker ruote dashboard webserver
22. which storage? managing while in prod ruote-fluo
23. Dashboard expression flow expression id
24. expression flow expression id • cancel(wfid_or_fei) • kill(wfid_or_fei) • pause/resume(wfid_or_fei) • replay_at_error(err) • re_apply(fei) Dashboard
25. expression flow expression id Dashboard • cancel(wfid_or_fei) • kill(wfid_or_fei) • pause/resume(wfid_or_fei) • replay_at_error(err) • re_apply(fei) • cancel process • cancel part of a process • pause/resume process • pause/resume part of a process • unblock a process in error • modify a process on the fly
29. which storage? managing while in prod ruote-fluo
32. is it worth it?