Audit Your Reactive Architectures!
summary
audit-reactive is a tool that detects concrete blocking API calls inside JVM reactive applications by bytecode weaving at startup and by compilation-time checks. It encodes ~500 rules over the JDK and common libraries, emits runtime alerts with thread and stack information, reports which methods block and how often, and points to where to change code or add annotations so instrumented builds catch issues during integration tests.
AI-written summary · about
chapters (29)
- 0:00Overture
- 0:43Non-blocking architecture
- 2:06Reactive architecture
- 3:32Identifying blocking calls
- 4:17The 3 strategies
- 7:20Strategy #2
- 8:43Strategy #4
- 10:20Strategy #5
- 11:51Strategy #6
- 12:20Strategy #7
- 13:39Strategy #8
- 14:30Strategy #9
- 16:55Strategy #10
- 18:10Strategy #11
- 18:57Strategy #12
- 20:05Strategy #13
- 21:43Strategy #14
- 23:19Strategy #15
- 26:18Strategy #16
- 27:50Strategy #17
- 28:44Strategy #18
- 31:18Strategy #19
- 36:06Strategy #20
- 37:09Strategy #21
- 38:38Strategy #22
- 39:56Strategy #23
- 41:48Strategy #24
- 43:09Strategy #25
- 44:22Strategy #26
related talks
43mMonitoring Reactive Applications
41mMonitoring Reactive Applications
51mSecurity Observability 101: Thinking Inside the Box!
17mFrom Reactive to Proactive: Event-Driven Architectures for Modern...
43mObservability for React applications
28mBuilding Observability for 99% Developers
01h 10mObservability For (Java) Devs - 2023 Edition
48mSetting up monitoring for Java apps