PubSub event streaming for Intellum data
Developers keep warehouses and internal systems current with PubSub, which streams creates, updates and deletes on users, courses, enrollments, assessment responses and purchases to Google Pub/Sub or AWS SNS in near real time. Intellum sets up the topic, and your developers build the consumer.
Common uses of PubSub event streaming
- Data engineers stream enrollments and assessment responses into the organization’s warehouse.
- Commerce managers trigger downstream entitlements from Intellum purchase events.
- IT keeps internal systems in sync with every user, course and enrollment change.
How PubSub event streaming works
Your organization opens a ticket with Intellum and picks Google Pub/Sub or AWS SNS. For Google, Intellum creates the topic and grants your service account subscribe access, and you create a pull or push subscription. For AWS, you create a customer-managed encryption key and share its identifier.
Every create, update and delete on users, courses, enrollments, assessment responses and purchases then arrives in near real time. Each message carries the full record, related records, before and after values, the request type and a timestamp.
How to set up PubSub event streaming
Intellum Systems Engineering and Professional Services set up the topic as a scoped project. Your developers build the consumer.
- A Google Cloud or AWS environment
- Developers who can consume a message stream
- One destination per account: Google Pub/Sub or AWS SNS
How Intellum PubSub handles access and data
- Excluded data: messages never include passwords, API keys, payment card details or OAuth secrets and tokens.
- Personal data: user records in messages identify people, so treat the stream as personal data.
- Delivery: Google delivery uses a topic in Intellum’s project with subscribe access for your service account. AWS delivery uses SNS with your customer-managed encryption key.
- Ordering: delivery is at least once and unordered, so consumers must handle repeated messages safely.
- Environments: use separate subscriptions or topics for each environment.
What to know about PubSub event streaming
- The feed has no history and starts when the topic is created. Load existing data through the Intellum API first.
- Changes that only touch timestamps are not published.
- Each account streams to one destination.
Questions about PubSub event streaming
Pub/sub is a messaging pattern: a publisher sends messages to a topic, and subscribers receive them. Intellum publishes every create, update and delete on users, courses, enrollments, assessment responses and purchases to your Google Pub/Sub or AWS SNS topic.
In near real time after each create, update or delete in Intellum. Delivery is at least once and unordered, so consumers must handle repeated or out-of-order messages safely.
Either works, with one destination per account. For Google, Intellum creates the topic and your service account gets subscribe access. On AWS, SNS delivery uses a customer-managed encryption key that your team creates and shares with Intellum.
No. The feed starts when the topic is created and carries changes from that point on. Load existing records through the Intellum API first, then use PubSub to keep them current.
See PubSub event streaming working with your stack
Walk through this integration, and the questions IT will ask, with an Intellum expert.