Skip to content

Architecture and technical solutions

Future Factory

Version number: 1

Classification: Public

Responsible person: Overflow

Introduction

*This document will explain this project more in detail.*

Overview

*What do you need to know if you continue working on this project*

  1. Take a good look on requirement specification document
  2. This service works with the service related customer paths as described in the document above
  3. Next step is to implement login to HAKA login service with SAML 2.0 we did some work on it already.\ We used itfoxtec package and Okta developer portal but we didnt finish it fully bug free.\ You could probably use some other solutions such as using Keycloak as a identity broker for HAKA and geting the login information from there or something.
  4. Take a look at the Documents for database
  5. Take a look at source code repositories

Technologies used

  • Frontend: React
  • Backend: ASP.NET Core
  • For database: Postgresql
  • For testing: Robotframework, Selenium
  • Microsoft Power Automate
  • Kubernetes
  • Gitlab CI/CD

Source code repositories

All the repositories have read me files you should take a look att

Descriptions of product development environments

Test environments we tried to do were done in CSC cloud with following architecture in mind. Also I dont recomend running database on the Kubernetes cluster. You can use our docker compose to quickly run your database.

We didnt manage to do complete CI/CD pipeline with different environments to deploy our code.

That is something you have to implement if you want to develop this project further and make your life easier for future. Also maybe look for other ways to do different environments.

Developing further

  • Make HAKA login with SAML bug free and working.
  • Production enviroment with all the needed stuff for actual use. Domains, hosting and such.
  • CI/CD only makes Docker containers and deploys to our test Kubernetes cluster. Make this better suit your needs.

The most important technical solutions on which the product relies

For further development its good to take look att these things.

Interfaces

Frontend-admin test interface

Frontend test interface

backend swagger page

Description of the execution environment (production)

Production environment execution is up to you :D

Database descriptions

Documents for database