Strangler Pattern in practice

1

RancherOS

The docker images ready for deployment were built on the pushed git tag. We used the Rancher tool for test/stage environments.

#Linux #Operating Systems #Linux Distribution 3 social mentions

2

PHPUnit

So what to test? We decided to test what the client recognized as key functionalities. For the client, most of the functionality is crucial, we had to use our intuition. Of course, no one is able to write tests for an unknown existing system that will cover everything, having no budget for it. We used PHPUnit. We have also added smoke tests (does it return "200"?) to most of the subpages that we managed to find by clicking.

#Development #Online Services #Automated Testing 30 social mentions

3

Kubernetes

Sometimes a product becomes popular. Traffic is increasing, we are opening up to new markets. We have come to the point where we had to migrate to the cloud. We choose Google Cloud and Kubernetes. The fact that we used the docker from the beginning was helpful. We had sessionless authentication, filesystem abstraction, all infrastructure in docker, we were cloud-ready, so that's happened.

#Developer Tools #DevOps Tools #Containers As A Service 280 social mentions

4

JSON Web Token

For example, logging into the system was one of the first. Remember how it worked so far? The user logged in in legacy, his username was saved in the session (memcached) and the username in the new part was taken from the session, after which the user could be authorized in both. Now we had to reverse this mechanism. By the way, we decided to stop using the memcached session and replace it with the JWT token passed in the cookie. This was also necessary later to be able to scale the app in the Cloud (sessionless authentication).

#Identity Provider #Identity And Access Management #SSO 276 social mentions

5

Google Cloud Platform

Sometimes a product becomes popular. Traffic is increasing, we are opening up to new markets. We have come to the point where we had to migrate to the cloud. We choose Google Cloud and Kubernetes. The fact that we used the docker from the beginning was helpful. We had sessionless authentication, filesystem abstraction, all infrastructure in docker, we were cloud-ready, so that's happened.

#Cloud Computing #Backend As A Service #Cloud Infrastructure 167 social mentions

6

Blackfire.io

The problems were like with any legacy application. It was necessary to patch urgent bugs and optimize the code in some parts. We mainly used Blackfire and MySQL Slow Query Log to monitor and look for the causes of problems.

#Monitoring Tools #Log Management #Application Performance Monitoring 11 social mentions