...
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
The provisioning of Authenticated Topics and the subsequent publish/subscribe actions on that Authenticated Topic rely on the proper AAF Permissions to be granted to various Identities.
The following Identities are referenced:
- IdentityMR - the AAF Identity used by Message Router to access AAF and perform authorization checks.
- IdentityTopicMgr - the AAF Identity used by Bus Controller to access AAF and create Permissions and Roles, and grant those Permissions to Roles and Identities.
- IdentityPub - the AAF Identity used by the publisher of the Topic when accessing the MR API. The fully qualified Identity typically belongs to a namespace related to the application. i.e. IdentityPub@NamespacePub
- IdentitySub - the AAF Identity used by the subscriber of the Topic when accessing the MR API. The fully qualified Identity typically belongs to a namespace related to the application. i.e. IdentitySub@NamespaceSub
Pre-requisites:
- Identities created in AAF
- Credentials for Identities available in kubernetes values (probably as Secrets)
- IdentityTopicMgr has access permission granted for all Application Namespaces
| Gliffy | ||||
|---|---|---|---|---|
|
Provisioning for Data Router Clients
...