filmov
tv
8.1 Orchestrating fibers termination in Crystal - Live coding a URL checker in Crystal
Показать описание
You might have noticed that, as our concurrent application grew in complexity, some fibers started "escaping" our termination strategy.
1. Our app features two independent pipelines, one reading from the web and writing to an in-memory store, and one reading from that in-memory store and writing to a UI. We currently signal user-required termination to both, but only wait for the UI pipeline to shutdown. Let's fix this!
2. When CTRL+Cing out of the app, you might occasionally observe some stacktraces being printed on the console. These are due to some unsupervised fibers spawned by our own Enumerable#» method. Let's refactor the code to avoid instantiating those fibers altogether.
You can find the code we wrote during the session here:
1. Our app features two independent pipelines, one reading from the web and writing to an in-memory store, and one reading from that in-memory store and writing to a UI. We currently signal user-required termination to both, but only wait for the UI pipeline to shutdown. Let's fix this!
2. When CTRL+Cing out of the app, you might occasionally observe some stacktraces being printed on the console. These are due to some unsupervised fibers spawned by our own Enumerable#» method. Let's refactor the code to avoid instantiating those fibers altogether.
You can find the code we wrote during the session here:
0:57:48
0:16:45
19:46:35
0:45:46
0:20:52
0:11:07
0:05:27
0:23:29
0:49:38
0:36:17
1:52:01
0:13:37
0:42:46
0:33:13
0:28:41
1:00:14
1:55:58
0:15:04
1:04:51
0:44:40
1:12:20
2:57:09
1:38:26
0:35:34