* Group service provide CRUD operations for group management.
* This service is integrated with UserOrg service to fetch group member data. So APIs which handle group member details uses UserOrg service. System settings like custodian organisation id or default organisation id is fetched from UserOrg. Organisation details are read using Org read API from UserOrg.
* Most of the group CRUD operations generate notifications to users using Notification Service (eg: Group Created)
* Content Service is used to search the activity details with respect to the activity type and id using activityConfig.json.
* Cassandra is the primary data store and Redis is used for caching the group data.
* Every API call generates telemetry and with the help of logstash-logback, this telemetry is updated to "${ENV\_NAME}.telemetry.raw" Kafka topic. Datapipeline of Sunbird-Obsrv process this telemetry for various data operations.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://lern.sunbird.org/use/developer-guide/groups/architecture.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.