📄️ Introduction
In order to create a new rac-delta implementation, it is recommended to follow rac-delta core features and interfaces, to maintain coherence and functionallity with every SDK available.
📄️ Interfaces
Interfaces are important to know how rac-delta objects are represented whithin the SDK and what parameters are needed for operations of the protocol.
📄️ Configuration
In order to achieve a proper working rac-delta implementation, configuration properties are important.
📄️ Storage Adapter
Storage Adapter is a special service that will implement the selected storage using the configuration seen on configuration. As rac-delta is storage agnostic, having an abstraction for storage is a perfect solution.
📄️ Services
In order to organize and to use rac-delta properly, it is important to atomize responsibilities of the protocol in different services.
📄️ Pipelines
Pipelines are optional, but a recommended way to unify all services and configuration into one coherent pipeline that follows the protocol perfectly.