c150871a94
* Updated saga to JUnit 5 * Update fix for CI job in trampoline module * Updated update-method module to JUnit 5 * Upgraded to latest JUnit Jupiter JUnit 4 is not needed when using JUnit-Vintage * Reverted change to access modifier on Trampoline * Cleanup to resolve code smells * Formatting * Formatting * Migrating to JUnit5 and updating some Mockito patterns * Migrating to JUnit5 * Migrating to JUnit5 * Migrating to JUnit 5 * Formatting cleanup * Added missing scope for junit * Fixed tests that were not running previously. Co-authored-by: Subhrodip Mohanta <hello@subho.xyz>
layout, title, folder, permalink, categories, tags
| layout | title | folder | permalink | categories | tags | |
|---|---|---|---|---|---|---|
| pattern | Half-Sync/Half-Async | half-sync-half-async | /patterns/half-sync-half-async/ | Concurrency |
|
Intent
The Half-Sync/Half-Async pattern decouples synchronous I/O from asynchronous I/O in a system to simplify concurrent programming effort without degrading execution efficiency.
Class diagram
Applicability
Use Half-Sync/Half-Async pattern when
- a system possesses following characteristics:
- the system must perform tasks in response to external events that occur asynchronously, like hardware interrupts in OS
- it is inefficient to dedicate separate thread of control to perform synchronous I/O for each external source of event
- the higher level tasks in the system can be simplified significantly if I/O is performed synchronously.
- one or more tasks in a system must run in a single thread of control, while other tasks may benefit from multi-threading.