The main task for the .NET engineering team was the development of the back-end application as a service. It was needed to make an integration of external time monitoring systems with the customer’s business management platform.
Development of the Back-End Application for Time Monitoring Based on Microservices
- Сustomer’s business management platform gained a new service for tracking time of the employees
- Thanks to the new functionality the customer was able to offer his clients more control over their employees
The main task for the .NET engineering team was the development of the back-end application as a service. It was needed to make an integration of external time monitoring systems with the customer’s business management platform.
Business Challenge
The customer has his own business management platform that is already widely used by his clients. The customer has analyzed the market and decided that the platform needs an additional service that will be responsible for the tracking & monitoring of the employee’s working time. On the one hand, the development of a new service had to satisfy current partners and give them more control over their resources. On the other hand, this decision was supposed to help attract new clients.
Solution
The development team took over the development of the back-end app that collected data from third-party APIs. All the data was of the same type and was intended for the tracking of the employee’s working time f.e. when the person started the work, when she left, how many breaks she had etc. After data collection, the application processed it, selected the necessary information, and saved it to the database for further processing by the customer’s application. The application was based on microservices architecture, services communicated with each other through Azure Service Bus, data was stored in Mongo and MS SQL
The microservice development was based on the DDD approach and the Clean Architecture approach. The Foundation package was used to work with the Service bus. To implement communication between projects, the Mediator pattern of behavior was used, for working with databases – the Generic Repository. The entire infrastructure was deployed on Azure, in particular, the Azure board, Pipelines, Repos, Azure SQL server, and application insights were used.
Summarizing, Chudovo engineers were involved in the following activities:
- Development of the project from scratch
- Building distributed applications
- Development of the main functionality
- Development and support of document templates
Business Impact
The developed service became an organic part of the customer’s business management platform and expanded its main functionality. Working with the .NET dedicated development team the customer received the combination of scalable and high-quality software solutions from the technical point of view. The customer could cover one of the needs of the users of his platform and bring employee monitoring to a new level. Thanks to the functionality of time tracking, platform users can rationally plan and allocate their resources within the company.
- Сustomer’s business management platform gained a new service for tracking time of the employees
- Thanks to the new functionality the customer was able to offer his clients more control over their employees