Web, Mobile
- Payments
Category
Development
Client
DTEK
Industry
Utility, Payments
Platforms
iOS

Digital Platform for
Utility payment
for customers
- + Research
- + UX/UI Design
- + Front-end Development
- + API to Legacy
- + Payment Processing


A digital utility-payment service
for 5.6 millions of users
Industry: Utility Payments Platforms: Web, Mobile Client’s geography: Ukraine

About the Business
Project Tasks
TEAM: 2 UI/UX designers / 3 Front-end engineers / 3 Back-end engineers / Solutions Architect / SAP Web Services Engineer / DevOps / 2 QA specialists / Project manager / Business analysts
TECH STACK:TypeScript, Vue.js, Vuex, Nuxt.js, Java / Spring, Node.js / Express.js. SAP, MySQL, REST API, Swagger, WebSockets / Socket.io, GraphQL, Apache Ignite, Maven.
PROJECT DURATION: 16 months



Platform Features
Integration with SAP via web services
Front-end and back-end clustering; Caching with Apache Ignite; JWT authorization
Fault-tolerance up to 6,000,000 users

Integration with the Back-end by REST API
Middleware for filtering HTTP requests on Node.js
UX design and unique front-end application logic
FRONTEND
Vue.js (Nuxt), Webpack, SCSS, Pug, ES6, Node.js, express.js. It consists of two parts: SPA Vue.js (Nuxt), which is responsible for the user interface, and the Node.js application (Frontend cluster), which is responsible for receiving, validating and sending data to the backend application in JSON format via the REST API.

BACKEND:
Using Java (Spring framework), Tomcat, and Maven, the backend cluster handles data from Node.js, exchanges data with SAP dispatchers (SAP CRM, SAP ISU), manages database storage (MS SQL cluster), processes non-SAP user data, and caches static data and session tokens (Apache Ignite cluster).


For those of us who are blessed with good sight. So we seldom consider it. That’s why going off to investigate the whys and hows involved is a little like trying to get behind the wind