...
The goal of the colector is to support high volume data. It uses plain TCP connections tunneled in SSL/TLS. Connections are stream-based (as opposed to request-based) and long running. Payload is binary-encoded (currently we are using Google Protocol Buffers). HV-VES uses direct connection to DMaaP's Kafka. All these decisions was made in order to support high-volume data with minimal latency. This way xNFs (VNFs and PNFs) can send for instance Real Time Performance Management data to ONAP for the analysis.
Contributing
Rules
TODO
Technology stack
...
Implementation details
Technology stack
- Project Reactor is used as a backbone of the internal architecture
- Netty is used by means of reactor-netty library.
- We are using Kotlin so we can get write very concise code with great interoperability with existing Java libraries
Rules
- Do not block. Use non-blocking libraries. Do not use block* Reactor calls inside the core of the application.
- Pay attention to memory usage.
- Do not decode the payload - it can be of a considerable size. The goal is to direct the event into a proper Kafka topic. The routing logic should be based only on VES Common Header.