Service Architecture
Microservice reusable building blocks architecture
DIGIT consists of several reusable building blocks on top of which one can develop a citizen service delivery solution. Read on to learn more about the microservice building blocks architecture.
Microservice - Building Blocks
To develop a new service, one needs to create a microservice and make it available through the API gateway. The API gateway calls the User Service for authentication and the Access Service for authorisation. The service developer can configure the roles and map the roles and actions using the Master Data Management Service.
Citizen Dashboard - The service user interface can be developed as part of the Citizen Dashboard or can be an independent solution. The citizen can log in using a mobile number and OTP. They can apply for a new service using the service UI. The File Store Service allows users to upload relevant documentation.
The Persister Service stores the submitted application asynchronously into the registry. The PII data is encrypted using the Encryption Service before storing. All changes are digitally signed and logged using the Signed Audit Service (ongoing). The Indexer Service transforms and enriches the application data. The Indexer Service also strips the PII data and sends it to the Analytics Data Store(ElasticSearch).
The Dashboard Backend Service executes configured queries on the stripped data and makes the aggregated data available to the Dashboard Frontend for the administrator or employee view. The views are in accordance with the user role access which is also configurable.
The Billing Service generates a demand based on the calculation logic for the given service delivery. Based on this demand, a bill is generated against which the payment has to be made. The citizen can either make an online payment or can pay at the counter (offline payment). The Payment Gateway Service is called for online payments and this is integrated with third-party service providers. The service routes the citizen to the service provider's website and then back to the citizen's UI once the payment is successful.
The Collection service is the payment registry and records all the successful payments. For offline payments, a record is made in the collection service after the collection of the Cash/Cheque/DD/RTGS. The allowed payment modes are configurable. The PDF service is used to generate receipts based on a configurable template.
The service then triggers the Workflow Service to assign tasks for verification and approval. Workflows can be configured. The Employee Service allows employee registrations and enables them to log in using the Employee Dashboard. The dashboard displays the list of pending applications as per the employee's role. The employee can perform actions on these applications using the employee UI for the service.
As the status changes or actions are taken on the applications the relevant SMS and Email Notification Service sends the updates to the applicant. Once the application is approved, the applicant can download the final certificate which is generated using PDF Service.
DIGIT has multi-tenant configuration capabilities. The Location Service allows the configuration of the tenant hierarchy and maps multiple tenants like Country, State, District or State, Department, and Sub Department. Each tenant can have their own configurations for service, roles, workflows etc. This allows for variations across different agencies in tune with the local context.
The Language Service facilitates the support of multiple languages in DIGIT. This service stores the translations in multiple languages.
Core Service & Kafka Topics Mapping Details
The table below provides the mapping of various core services to Kafka topics used in a DIGIT-based system.
🔄 Workflow Topics
egov-workflow-v2
save-wf-transitions
egov-workflow-v2-persister.yml (persister)
Persists workflow transition events
egov-workflow-v2
save-wf-businessservice
egov-workflow-v2-persister.yml
Saves a workflow business service config
egov-workflow-v2
update-wf-businessservice
egov-workflow-v2-persister.yml
Updates an existing workflow service
📝 Service Request Topics
service-request
save-service-definition
service-request-persister.yml
Save a new service definition
service-request
save-service
service-request-persister.yml
Save an actual service instance
📤 Data Uploader Topics
egov-data-uploader
infra.data.upload
DataUploadConsumer.java (egov-data-uploader)
Triggers data upload
egov-data-uploader
save-upload-jobs
uploader-persister.yml, egov-uploader-indexer.yaml
Saves details of upload jobs
egov-data-uploader
update-upload-jobs
uploader-persister.yml, egov-uploader-indexer.yaml
Updates upload job status/info
🧾 Audit Topics
audit-service; egov-persister
audit-create
audit-service-persister.yml
Logs audit records
audit-service; egov-persister
process-audit-records
Processes audit logs
egov-user; report
audit_data
Transfers audit data
📱 Notifications (SMS, Email)
egov-user; user-otp
egov.core.notification.sms
Send SMS notifications
egov-user; user-otp
egov.core.notification.email
Send email notifications
user-otp
egov.core.notification.sms.otp
Send OTP via SMS
📊 National Dashboard Topics
national-dashboard-ingest
nss-ingest-keydata
nss-persister.yml
Ingest NSS key data
📦 MDMS Topics
mdms-v2
save-mdms-schema-definition
mdms-persister.yml
Save schema definitions
mdms-v2
save-mdms-data
mdms-persister.yml
Save MDMS data
mdms-v2
update-mdms-data
Update MDMS data
🌐 Boundary Service Topics
boundary-service
dss-collection
For DSS data collection
boundary-service
service-consumer-topic
Used by service consumers
boundary-service
create-boundary-entity
Create new boundary entities
boundary-service
update-boundary-entity
Update boundary entities
boundary-service
save-boundary-hierarchy-definition
Save boundary hierarchy definition
boundary-service
update-boundary-hierarchy-definition
Update boundary hierarchy definition
boundary-service
save-boundary-relationship
Save relationships between boundaries
boundary-service
update-boundary-relationship
Update boundary relationships
👤 User Events
egov-user-event
save-user-events
Save new user events
egov-user-event
update-user-events
Update user events
egov-user-event
user-events-lat
Possibly used for LAT tracking
egov-user-event
persist-user-events-async
Async user event persistence
egov-user-event
update-user-events-async
Async user event update
🔍 Indexer Topics
egov-indexer
save-index-jobs
Save indexing job details
egov-indexer
update-index-jobs
Update indexing job info
egov-indexer
save-service-db
Save service DB entry
egov-indexer
update-service-db
Update service DB entry
🤖 Chatbot Topics
chatbot
chatbot-conversation-state-insert
chatbot.yml (persister)
Insert conversation state
🚪 Gateway Topics
gateway
res-filter
For async filtering
Last updated
Was this helpful?