Microservices in the Brightspace Cloud
Download 120.79 Kb.
|
- Navigate this page:
- Distributed Event Framework Service
Dates ServiceDescription The Dates Service provides an API for learner dates, for example, Brightspace Pulse uses the Dates Service to provide details on assignment due dates and scheduled exams. Location A global cluster that resides in AWS. The Dates Service Database resides in IBM Cloudant. Dependencies Depends on the Authentication Service and Landlord Service, and User Info Service. Depended on by Brightspace Pulse.
To communicate, devices and microservices use the HTTPS networking protocol. While in transit, all data is encrypted; however, data at rest is not encrypted. The userID in data is a composite key along with the course offering ID; it is not a universally accepted global ID for the user. The user ID cannot be linked to a user's name or identity. In the database, user IDs appear as a series of repeated numbers. Regarding data retention, D2L requires the user ID to report on general user data; it is not used to report on the activity of a specific user. For example, the user ID may be used to report on how many users have an average of three or more dates per month. D2L would not use the data to report on how many times John Smith looks at his deadlines. D2L retains the data as long as required to generate reports based on general user data. The reports are subject to change at D2L’s discretion and client-specific data is subject to the terms specified in the MA, including data retention past contract termination.
How the Service Works
11.The request is forwarded to the Dates Service. 12.If the data is stored in Brightspace Learning Environment, the data is retrieved using the Valence API. If the data is not stored in Brightspace Learning Environment, the data is retrieved from the Dates Service database. 13.The date information is then sent to the device.
Figure : How the Dates Service works when accessing dates from Brightspace Pulse Distributed Event Framework ServiceDescription The Distributed Event Framework Service provides awareness of Brightspace Learning Environment events for other products such as Brightspace Insights. Location One instance per Data Center. Note D2L is evaluating a solution that will provide Brightspace Insights in the cloud for on-premise Brightspace implementations. As such, the Distributed Event Framework Service is currently only available in D2L Data Centers.
Depends on the Landlord Service. Depended on by the Brightspace Data Platform.
The Distributed Event Framework Service transmits and stores data in the form of events. The Distributed Event Framework Service uses the Advanced Message Queuing Protocol (AMQP) with encryption. While in transit, all events are encrypted. The events that are transmitted contain programmatic identifiers for the user, the context of the event, and the type of the event. For example: A programmatic identifier for the user such as User ID = 123. A programmatic identifier for courses such as Course ID = 987. Events such as logins, tool access, and content visits are identified by the programmatic identifier for the user. Events are stored in the Data Center and transmitted to services such as the Brightspace Data Platform (located in AWS). How the Service Works The following example illustrates how the Distributed Event Framework Service works with Brightspace Insights.
14.These events are then stored in the Main DB split. 15.The Telegraph Service pulls batches of events from the Main DB split and prepares to publish them to the Distributed Event Framework Service. 16.Before publishing events, the Telegraph Service must attach a TenantId to each event. It first looks for the TenantId in the Memcache (where a cached copy of the TenantId may be stored). If the TenantId is not there, it requests it from the Landlord Service. 17.The Landlord Service returns the unique TenantID to the Telegraph Service, which attaches the TenantId to each event and then publishes the events to the Distributed Event Framework Service. 18.The Distributed Event Framework Service processes the events for usage by other products/services. For example, the Distributed Event Framework Service streams events to the Brightspace Data Platform.
Figure : How the Distributed Event Framework Service works with Brightspace Insights Directory: ecat -> help -> browser -> documents documents -> Brightspace Platform Requirements 1 Document Change History 1 Brightspace Platform Requirements 2 Brightspace Apps 5 About D2L 9 help -> - documents -> Brightspace Platform Requirements 1 Brightspace Apps 4 About D2L 9 ecat -> The production of speech sounds 1 Articulators above the larynx ecat -> Connected speech and coarticulation Download 120.79 Kb. Share with your friends:
|
