First, niologic documented the architecture, the state of technological development and plans for further development. In cooperation with the sales department, the legal department and our customer’s IT security division, Microsoft Azure™ and Google Cloud™ were evaluated as possible alternatives to Amazon AWS™.
At the same time, as part of a pilot study, niologic developed a modularization of the existing SaaS solution as a cloud native container solution (docker) with Kubernetes functioning as a container orchestrator.
This solution, including docker images, load balancing and SSL termination, cloud storage, Kubernetes configuration, backup creation, integration of OKTA™ as a SSO solution and fitting of the monitoring, was implemented within 5 project days using rapid prototyping. Also, a hadoop cluster was implemented and configurated with Apache Spark 2.0. After the deployment and the evaluation of Microsoft Azure and Google Cloud our customer decided to use Google Cloud as a service provider.
niologic supported their customer with the initial setup and every day usage of the solution. For this purpose, a team consisting of site reliability engineers (SRE) was set up as a DevOps solution and initiated by niologic using Kanban in product management.
niologic instigated the introduction of Kubernetes Helm, Stackdriver Application Performance Monitoring (APM) ,Terraform for Infrastructure as Code, as well as alerts for monitoring the Kubernetes cluster.
Further improvement of the hadoop cluster was conducted using Google Dataproc™ and preemptible VMs. Given entities and data bases were laid down into a migration plan and were finally migrated by niologic and the SREs.
Being coached by niologic, our customer’s developers took charge of the software’s and the connected container’s maintenance using Continuous Integration (CI) and Continuous Deployment (CD) pipelines.