eMACH-Sigma Microservices
As part of the move towards microservice-oriented development, eMACH-Sigma offers the following features as microservices. These microservices shall be provided as Docker container images, which can be deployed on your project or application Dockers.
Sigma Studio Microservice
Sigma UI Microservice
Sigma Schedule Engine Microservice
Sigma Studio Microservice enables creation and maintenance of dashboards and reports. It facilitates the configuration of a single data source or collating the data from multiple data sources through data composer, which involves setting up connections to various databases, APIs, or other data repositories. In addition, the Studio Engine handles the configuration of individual reports and report groups, allowing users to define parameters, templates, layouts, logos, charts for the reports and also defining the sharing of reports/report groups through various delivery methods such as SMTP, FTP, Amazon S3 and notify through SNS. It also manages Report Bursting configurations, which enables the distribution of a single report/report group to different recipients based on specific criteria. Furthermore, the Studio Engine supports dashboard creation by enabling the design and configuration of visual data representations, including grids and charts. It oversees administration settings, which focuses on entitlements of data, reports and dashboards.
Sigma UI Microservice enables users to access the dashboards and reports created through Sigma Studio. The Sigma UI handles creation of derived reports that can be used to customize the report format, columns, grouping, filtering, sorting etc. It supports grouping of multiple reports/report groups into individual file, single sheet and multi sheet. It supports scheduling of reports according to users' needs at different frequencies. It also facilitates the sharing of reports through various methods such as SMTP, FTP and S3 BUCKET.
Sigma Schedule Engine Microservice focuses on managing and executing report schedules, ensuring that reports are generated and delivered as per predefined timings and conditions. The engine has a built-in Failure recovery mechanism to ensure 100% delivery rate during the day. It also handles end-of-day (EOD) retry processes (re-attempting and completing reports that fail during end-of-day processing). Additionally, Report bursting schedules are split into customer wise schedules for distributed and faster execution and delivery.