Modules
The "Modules" section defines the types of components to use, as follows.
"Modules" : { "Reader" : "File", "Sender" : "<SenderType>", "Serializer" : "Json", "StorageProvider" : "<StorageProviderType>", "TopicManager" : "File", "SchemaGenerator" : "Json", "SchemaRegistry" : "<SchemaRegistryType>" }
The Modules section components are listed in the following table.
Component | Type of... |
---|---|
"Reader" | Reader to use, which must be "File" in this release. |
"Sender" |
Sender to use, which can be one of: "Kafka", "Azure", or "File". These are referred to as SenderType. |
"Serializer" | Type of serializer to use. This must be "Json". |
"StorageProvider" | Type of external storage provider to use for storing over‑threshold size blob and slob data, which can be one of: "File" or "AzureBlobStorage". |
"TopicManager" | Topic manager to use, which must be "File" in this release. |
"SchemaGenerator" | Type of schema generator to use. This must be "Json". |
"SchemaRegistry" |
Type of "SchemaRegistry" to use for looking up and storing Event Schemas. This can be one of: "None" or "Azure", or "Confluent". |
The SenderType essentially selects the event streaming platform (or file sender for development and testing) and the appropriate client for the selected type. The selected SenderType determines which <SenderType>Sender section in the Configurations section will be used.
All required modules must be specified in the Modules section. The ESP checks for the presence of all seven modules; that is, Reader, Sender, TopicManager, Serializer, StorageProvider, SchemaGenerator, and SchemaRegistry.