...
Some considerations for choosing between Message Router and Data Router:
Attribute | Message Router | Data Router | Comments |
---|---|---|---|
Payload description | frequent, small (~KBs) messages | periodic, large sets of records (files) | |
Max payload size | 1 MB | x GB | |
Authentication Model | AAF Credentials via Basic Authorization | Local credentials via Basic Authentication | |
Persistence | Yes (kafka data store on PV) | Yes (Linux file on PV) | |
High Availability | Using ZK ensemble | Using horizontal scaling | |
Data ordering | Possible | Not guaranteed | |
Subscriber implementation | HTTP Client | HTTP Server | NOTE: the HTTP Server implementation implies the installation of a server SSL certificate. |
Some ways MR and DR are the same:
Attribute | Message Router | Data Router | Comments |
---|---|---|---|
Bus Architecture | Yes | Yes | Both use "publisher" and "subscriber" terminology for end points |
HTTP/HTTPS protocol | Yes | Yes | |
Data Expiration | Yes | Yes | NOTE: different default values. MR: 7 days. DR: 24 hours. |
Publisher implementation | HTTP Client | HTTP Client |
DMaaP Provisioning
Provisioning for Message Router Clients
Provisioning for Data Router Clients
...