...
- PDS
- partition data
- WAL records
- Metadata
- binary meta
- marshaller
- Communication SPI
- Discovery SPI
- Binary Marshaller
- Affinity.
- Management API
- argument
- results
- tasks (class names).
- ThinClient Protocol
Compatibility Matrix
| Component | Type | Number of releases |
|---|
| Ignite public API | backward | 1 |
| PDS | backward | all |
| WAL | backward | all |
| Metadata | backward | all |
| Thin Client | full | all |
| Communication SPI | full | 1 |
| Discovery SPI | full | 1 |
| Binary Marshaller | backward | all |
| Management API | backward | 1 |
| Affinity | full | all |
Current Ignite codebase
- Is there any primitives, building blocks to provide compatibility?
- Difficulties for day by day coding.
- Compatibility testing.
- explicit tests.
- ability to run tests with random node versions
- New feature implementation, enabling.
- patterns for implementing commons cases: new version of algorithmes, testing against new versions.
- Scope of compatibility:
- Currently any third-party module can register own ports (messages?) and must be able to track compatibility.
...
{"serverDuration": 98, "requestCorrelationId": "3b10794f1fbd059e"}