Sign up to save your podcasts
Or
Share Running Matomo with open source technologies such as Kubernetes and docker
Share to email
Share to Facebook
Share to X
Share to email
Share to Facebook
Share to X
Or
Running Matomo with open source technologies such as Kubernetes and docker
In this session we will talk about the Matomo SaaS we built and explain why we invested building a solution with Kubernetes & Docker.
At Digitalist we provide Matomo services for clients with high demands on performance, adoptability, professional support and privacy. Among our clients are some of the largest Swedish public sector organisations and they have very high demands on privacy and security.
When we started our Matomo offering in 2018 we looked into different technologies and services to use when we started building our SaaS. (Software as a Service or Matomo cloud)
After many internal discussion, investigations and evaluations of different services we decided to go for a Kubernetes bases solutions, even if we knew this was going to be a long journey of problem solving and innovations.
So why did we do it?
-We wanted to keep full control of the whole tech stack and be able to move the whole set up to basically any cloud service.
-We wanted full traceability (version control of everything we do (not only in Matomo)
-We wanted to have full control of security. This includes all components in a system (not just Matomo).
-We wanted to build a solutions that we could scale out to handle a lot of data (on the fly)
-We wanted a solutions that we could offer to a lot of clients (we needed a high level of automation).
-We wanted a solution where we could do individual adjustments for specific clients that have these needs.
View all episodes
By In this session we will talk about the Matomo SaaS we built and explain why we invested building a solution with Kubernetes & Docker.
At Digitalist we provide Matomo services for clients with high demands on performance, adoptability, professional support and privacy. Among our clients are some of the largest Swedish public sector organisations and they have very high demands on privacy and security.
When we started our Matomo offering in 2018 we looked into different technologies and services to use when we started building our SaaS. (Software as a Service or Matomo cloud)
After many internal discussion, investigations and evaluations of different services we decided to go for a Kubernetes bases solutions, even if we knew this was going to be a long journey of problem solving and innovations.
So why did we do it?
-We wanted to keep full control of the whole tech stack and be able to move the whole set up to basically any cloud service.
-We wanted full traceability (version control of everything we do (not only in Matomo)
-We wanted to have full control of security. This includes all components in a system (not just Matomo).
-We wanted to build a solutions that we could scale out to handle a lot of data (on the fly)
-We wanted a solutions that we could offer to a lot of clients (we needed a high level of automation).
-We wanted a solution where we could do individual adjustments for specific clients that have these needs.