How playtikaoss/json-reactive works
Component Relationships
[Reactor/RxJava2 Consumers] → [ReactorObjectReader/Rx2ObjectReader]
• ↓
[NonBlockingObjectReader] ← [Jackson NonBlocking Parser]
• ↓
[Tokenizer] → [ByteBuffer Processing]
Special Elements
a) Data Flow Indicators:
• ByteBuffer input flow
• Reactive stream output (Flux/Flowable)
• Async boundaries
b) Key Interfaces:
• JsonFactory integration points
• ObjectMapper reader integration
Implementation Details to Highlight
• Non-blocking nature of the parser
• Transformation from raw JSON to POJO objects
• Where reactive backpressure is handled
Notes Section
Technical notes about:
• Thread model
• Backpressure handling
• Memory usage characteristics
• The clean separation between the reactive implementations (Reactor/RxJava2)
• The shared core non-blocking implementation
• The integration with Jackson's parser
• The reactive streaming nature of the data flow
Keep the abstraction level focused on the architectural components while showing the key technical decisions that enable non-blocking JSON parsing with reactive streams support.
The integration with Jackson's ecosystem
Remember to maintain a balance between showing the high-level architecture and the important technical details that make this library unique in its non-blocking, reactive approach to JSON parsing.