DIGIT-CORE-2.9-LTS

DIGIT 2.9 LTS

DIGIT 2.9 represents the most recent Long-Term Support (LTS) version, offering a stable and reliable foundation. This version emphasises enhanced security measures, improved system stability, streamlined deployment processes, simplified configuration, and comprehensive documentation. Periodic updates, encompassing both minor adjustments and significant enhancements, will be released as necessary. Support for this iteration of DIGIT will be available for the upcoming five years, with a clear migration guide available to facilitate the transition to subsequent LTS versions once the current support period concludes.

Benefits of Long Term Support

Extended Support: LTS versions come with an extended period of support, which includes security updates, bug fixes, and sometimes even minor feature enhancements. This extended support period will last for 5 years, which means that users do not need to upgrade to newer versions frequently to receive critical updates.

Stability: The LTS release is typically more stable than regular releases because it undergoes more extensive testing and bug fixing. Compatibility: With the extended support period, the LTS release ensures better compatibility with third-party applications and hardware over time. Developers and vendors have a stable base to target, reducing the frequency of compatibility issues.

Reduced Costs: For businesses, the reduced need for frequent upgrades can translate into lower IT costs. Upgrading to a new version often involves significant effort in testing, deployment, and sometimes even hardware upgrades. LTS releases help spread these costs over a longer period.

Predictability: LTS release provides a predictable upgrade path, making it easier for organisations to plan their IT infrastructure, training, and budgets. Knowing the support timeline in advance helps in strategic planning and resource allocation.

Focus on Core Features and Performance: Since the LTS release is not focused on adding new features aggressively, the bulk of efforts are spent on optimising for performance and reliability. This focus benefits users who need a solid and efficient system rather than the latest features.

Community and Vendor Support: LTS releases will often have a larger user base, which means a more extensive community support network is available.

What is new in LTS

• Infra/Backbone upgrade:

  • Postgres upgrade
  • Kafka upgrade
  • Redis upgrade
  • Kubernetes upgrade
  • Elasticsearch upgrade

• Use of helm file for deployment management

• Upgrade of core service dependencies

• Upgrade to DIGIT libraries

• Spring Cloud Gateway

• Test Automation script

• Single Click deployment using Github Actions

New Services in LTS

• MDMS V2 (Beta)

• Workbench (MDMS UI) (Beta)

• Boundary Service (Beta)

New Functionalities

• Admin UI to configure Master Data

• Functionality to define schema and attribute validation for master data

• Maintain master data in the database

• Hot reload of MDMS data

• Configurable Rate limiting for services using helm

• Deployment of DIGIT without any local tool setup/configuration (via browser)

• Ability to create and link boundary nodes using UI/APIs

• Geospatial queries like proximity search to locate boundary nodes

core_v2.9: Standalone CORE 2.9 Release

DIGIT CORE 2.9 release includes 2 new services, 1 new module, several technical, security features and bug fixes. The highlight of this release is the separation of Core from DIGIT.

• New Services and Modules: Signed Audit, Internal Gateway, Service Request.

• Technical Enhancements and Fixes:

1. Filestore Service:

• Fixed flow to store and retrieve files from Azure blob storage.

2. PDF Service:

• Fixed bug where _create API creates duplicate PDF for each request.

3. SMS Notification Service:

• Added API for sms bounce back tracking.

4. Mail Notification Service:

• Added support for attachments.

• Disabled consumer listening on sms topic.

5. User OTP Service:

• Added support for sending OTP via email by emitting email events.

• Removed DB timezone dependency.

6. User Service:

• Added fallback to default message if user email update localization messages are not configured.

• Fixed bug where updating citizen profile causes server error.

• Fixed bug where employee details are updateable via citizen profile update API.

7. Workflow Service:

• Introduced state level business service fallback as part of v2 business service search API.

• Separated out v1 and v2 APIs to maintain backward compatibility.

• Enhanced workflow service to send descriptive errors for bad requests.

8. Inbox Service:

• Introduced event based inbox and deprecated dependency on searcher-service for fetching inbox items.

• Separated out v1 and v2 APIs to maintain backward compatibility.

• Introduced a new API to get records based on the provided search criteria(analogous to searcher service).

9. Dashboard Analytics:

• Introduced feature to perform DIVISION operation on metric chart responses.

10. Location Service:

• Fixed bug where search on root level boundary type yields empty search response.

11. Privacy Exemplar:

• Data privacy changes for masking/unmasking PII data were introduced as part of this exemplar. Steps to enable data privacy at module level can be referred to as part of WS exemplar here - Detailed Steps to configure privacy in W&S module

12. Encryption Client Library:

• As part of privacy changes, enc-client library was introduced to support encryption-related functionalities so that every service does not need to call the encryption service.

13. National Dashboard Ingest:

• Added support to allow user with national dashboard adaptor role to ingest data regardless of the tenant the user belongs to.

14. Codegen:

• Enhanced codegen utility to support openAPI 3.0 specifications.

15. Persister:

• Enhanced persister to make it compatible with Signed Audit Service.

16. Human Resource Management Service:

• Fixed bug where employee search causes server error in single instance clusters.

17. DIGIT Developer Guide:

• Backend Guide - This guide provides detailed steps for developers to create a new microservice on top of DIGIT and deploy it on DIGIT cluster. A sample birth registration spring-boot module was developed as part of this guide.

• Frontend Guide - This guide offers a systematic view of how to create the application screens on DIGIT. Both citizen and employee frontend modules were developed as part of this guide.

Non-functional:

1. Dashboard Analytics Service:

• Load tested dashboard analytics and documented improvement in performance.

2. PDF Service:

• Performance testing of bulk PDF generation.

3. Billing Service:

• Performance testing of bulk bill generation.