Research into how coroutines can answer to today's problems with the help of virtual threads and how the opposite can also be true
| Version - Git-Tag | Git Hash | Purpose |
|---|---|---|
| 1.0.0 | d00c17e448a19c3653e3c86093161e508e35c06d | Could Virtual Threads Cast Away the Usage of Kotlin Coroutines. Just the documentation on Scribd |
| 2.0.0 | edfd0d882696f0b403cb7054387ed07d02d7a21e | Video Completion |
- Note: All services do not have a converter implemented. This is intentional with the purpose to simplify code. In production environments, the DTO layer should be separated from the Domain and that separation should be very clear for purposes of readability, but also in some cases for safety concerns.
Projects for comparisons:
- warehouse-fulfilment-mvc
- warehouse-fulfilment-webflux
- warehouse-fulfilment-coroutines
- warehouse-fulfilment-vt
Only for version 1.0.0:
warehouse-fulfilment-vt-coroutines
Experiments with non-blocking logs:
warehouse-fulfilment-webflux-non-blocking
- Java 21 Virtual Threads - Dude, Where’s My Lock?
- Coroutines, Java Virtual Threads and Scoped Values
- Embracing Virtual Threads
- How to use virtual threads with Spring Boot
- Context Switching Theory
- Thread Theory - DePaul University - Boston
